[feat] open api eval other

[dsf86]

What type of PR is this?

Check the PR title.

• This PR title match the format: [<type>][<scope>]: <description>. For example: [fix][backend] flaky fix
• The description of this PR title is user-oriented and clear enough for others to understand.
• Add documentation if the current PR requires user awareness at the usage level.
• This PR is written in English. PRs not in English will not be reviewed.

(Optional) Translate the PR title into Chinese.

(Optional) More detailed description for this PR(en: English/zh: Chinese).

en:
zh(optional):

(Optional) Which issue(s) this PR fixes:

[CozeLoop]

Performed server-side Go code review focused on concurrency safety, correctness, and API functionality. See inline comments for Must-Fix and Should-Fix items.

[dsf86]

invalid

[codecov]

Codecov Report

❌ Patch coverage is 80.24928% with 206 lines in your changes missing coverage. Please review.

Files with missing lines	Patch %	Lines
...uation/application/convertor/experiment/openapi.go	79.30%	96 Missing and 58 partials ⚠️
...odules/evaluation/infra/metrics/experiment/init.go	20.00%	20 Missing ⚠️
...modules/evaluation/application/eval_openapi_app.go	92.73%	10 Missing and 7 partials ⚠️
...api/handler/coze/loop/apis/eval_open_apiservice.go	0.00%	12 Missing ⚠️
...ckend/modules/evaluation/infra/rpc/data/dataset.go	0.00%	2 Missing ⚠️
...on/domain/service/target_source_loopprompt_impl.go	87.50%	0 Missing and 1 partial ⚠️

@@            Coverage Diff             @@
##             main     #288      +/-   ##
==========================================
+ Coverage   68.07%   68.36%   +0.28%     
==========================================
  Files         568      570       +2     
  Lines       50554    51562    +1008     
==========================================
+ Hits        34414    35248     +834     
- Misses      13469    13576     +107     
- Partials     2671     2738      +67     

Flag	Coverage Δ
unittests	68.36% <80.24%> (+0.28%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

Files with missing lines	Coverage Δ
...evaluation/application/convertor/common/openapi.go	100.00% <100.00%> (ø)
...nd/modules/evaluation/domain/entity/expt_result.go	57.29% <ø> (ø)
backend/modules/evaluation/domain/entity/param.go	54.54% <ø> (ø)
...tion/domain/service/evaluation_set_version_impl.go	92.59% <100.00%> (ø)
...evaluation/domain/service/expt_result_aggr_impl.go	74.20% <100.00%> (+0.04%)	⬆️
...d/modules/evaluation/domain/service/target_impl.go	75.16% <ø> (ø)
...on/domain/service/target_source_loopprompt_impl.go	89.48% <87.50%> (-0.43%)	⬇️
...ckend/modules/evaluation/infra/rpc/data/dataset.go	0.00% <0.00%> (ø)
...api/handler/coze/loop/apis/eval_open_apiservice.go	0.00% <0.00%> (ø)
...modules/evaluation/application/eval_openapi_app.go	91.80% <92.73%> (+0.56%)	⬆️
... and 2 more

... and 3 files with indirect coverage changes

---

Continue to review full report in Codecov by Sentry.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 4f1afba...94867a8. Read the comment docs.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[CozeLoop]

Summary: This PR introduces open API endpoints and application/domain changes, but several handlers return empty payloads instead of invoking the generated Kitex client, breaking functional correctness and contracts. Additionally, the dataset RPC adapter ignores the new exact version filter, risking wrong version selection; and the metrics initialization uses sync.Once in a way that can permanently block initialization if meter==nil on the first call. Please address the Must-Fix handler delegations, wire the version filter correctly, and adjust metrics initialization semantics. Route annotations should also be aligned with the actual router paths.

[CozeLoop]

[P1] Handler bypasses service invocation and returns empty payload
This endpoint validates input but never calls the underlying EvalOpenAPIService client. It responds with an empty JSON object, which breaks functional correctness and observability (no metrics, no domain logic). For consistency with other handlers in this file that use invokeAndRender, please delegate to the generated Kitex client:

Suggested change

	var err error
	var req openapi0.SubmitExperimentOApiRequest
	err = c.BindAndValidate(&req)
	if err != nil {
	c.String(consts.StatusBadRequest, err.Error())
	return
	}
	resp := new(openapi0.SubmitExperimentOApiResponse)
	c.JSON(consts.StatusOK, resp)
	invokeAndRender(ctx, c, localEvalOpenAPIClient.SubmitExperimentOApi)

This ensures request binding, RPC execution, error mapping, and standard response handling align with the existing pattern.

[CozeLoop]

[P1] Handler returns empty JSON instead of calling service
GetExperimentsOApi binds and validates the request but does not invoke the RPC service, returning an empty response. This breaks the endpoint contract and makes monitoring misleading. Align with existing handlers by delegating to the Kitex client:

Suggested change

	var err error
	var req openapi0.GetExperimentsOApiRequest
	err = c.BindAndValidate(&req)
	if err != nil {
	c.String(consts.StatusBadRequest, err.Error())
	return
	}
	resp := new(openapi0.GetExperimentsOApiResponse)
	c.JSON(consts.StatusOK, resp)
	invokeAndRender(ctx, c, localEvalOpenAPIClient.GetExperimentsOApi)

[CozeLoop]

[P1] Handler does not execute business logic
ListExperimentResultOApi validates the request and returns an empty payload. It should call the EvaluationOpenAPIService.ListExperimentResultOApi method to fetch results and metrics. Please use the standard delegation pattern:

Suggested change

	var err error
	var req openapi0.ListExperimentResultOApiRequest
	err = c.BindAndValidate(&req)
	if err != nil {
	c.String(consts.StatusBadRequest, err.Error())
	return
	}
	resp := new(openapi0.ListExperimentResultOApiResponse)
	c.JSON(consts.StatusOK, resp)
	invokeAndRender(ctx, c, localEvalOpenAPIClient.ListExperimentResultOApi)

[CozeLoop]

[P1] Aggregation endpoint returns empty response, missing service call
GetExperimentAggrResultOApi should invoke the RPC client to retrieve aggregator results. Returning an empty object will mislead clients and break contracts. Please delegate to the Kitex client:

Suggested change

	var err error
	var req openapi0.GetExperimentAggrResultOApiRequest
	err = c.BindAndValidate(&req)
	if err != nil {
	c.String(consts.StatusBadRequest, err.Error())
	return
	}
	resp := new(openapi0.GetExperimentAggrResultOApiResponse)
	c.JSON(consts.StatusOK, resp)
	invokeAndRender(ctx, c, localEvalOpenAPIClient.GetExperimentAggrResultOApi)

[CozeLoop]

[P1] Update handler does not call service
UpdateEvaluationSetOApi currently binds input and returns an empty response without invoking domain logic. This should delegate to the generated client to update the set and return a proper response:

Suggested change

	var err error
	var req openapi0.UpdateEvaluationSetOApiRequest
	err = c.BindAndValidate(&req)
	if err != nil {
	c.String(consts.StatusBadRequest, err.Error())
	return
	}
	resp := new(openapi0.UpdateEvaluationSetOApiResponse)
	c.JSON(consts.StatusOK, resp)
	invokeAndRender(ctx, c, localEvalOpenAPIClient.UpdateEvaluationSetOApi)