Please address the comments from this code review:

## Overall Comments
- The global `scanedItemNameList` slice is mutated from multiple actions without any synchronization, which could lead to data races in concurrent runs; consider encapsulating this state per-task or protecting it with a mutex.
- Several places in the autosell logic rely on magic constants and hard-coded substrings (e.g., default `targetPrice = 4600`, Chinese name fragments in `AutoSellStockRedistributionOpenItemTextAction`); centralizing these into configurable data (e.g., a table or config file) would make the behavior easier to extend and maintain.
- Some new autosell handlers assume non-nil args and images (e.g., `AutoSellStockRedistributionOpenItemTextRecognition.Run`, `AutoSellItemRecordAction.Run`) and reuse copy-pasted log messages (e.g., 'from AutoSellFriendsPriceRecognition'); adding nil checks and more precise log messages would make failures safer and debugging clearer.

## Individual Comments

### Comment 1
<location path="agent/go-service/autosell/autosell.go" line_range="111-113" />
<code_context>
+
+type AutoSellStockRedistributionOpenItemTextRecognition struct{}
+
+func (r *AutoSellStockRedistributionOpenItemTextRecognition) Run(ctx *maa.Context, arg *maa.CustomRecognitionArg) (*maa.CustomRecognitionResult, bool) {
+
+	detail, recoErr := ctx.RunRecognition("AutoSellStockRedistributionOpenItemText", arg.Img)
+	if recoErr != nil || detail == nil {
+		log.Error().Err(recoErr).Msg("Failed to run AutoSellStockRedistributionOpenItemText")
</code_context>
<issue_to_address>
**issue:** Missing argument nil checks in recognition handler can cause panics.

This method assumes `arg` and `arg.Img` are non-nil, unlike `AutoSellPriceCompareRecognition.Run`. If the framework passes a nil arg or image (e.g., after an upstream failure), `ctx.RunRecognition` will panic. Please add the same defensive nil checks here to match the other recognition handler.
</issue_to_address>

### Comment 2
<location path="agent/go-service/autosell/autosell.go" line_range="52" />
<code_context>
+		} `json:"filtered"`
+	}
+	// Results.Best是空，暂时只能这样获取
+	if detailJsonErr := json.Unmarshal([]byte(detail.CombinedResult[2].DetailJson), &detailJson); detailJsonErr != nil {
+		log.Error().Err(detailJsonErr).Msg("Failed to parse DetailJson from AutoSellFriendsPriceRecognition")
+		return nil, false
+	}
</code_context>
<issue_to_address>
**suggestion:** Log message references the wrong recognition name, which can hinder debugging.

This error is logged in `AutoSellStockRedistributionOpenItemTextRecognition`, but the message still mentions `AutoSellFriendsPriceRecognition`. Please update the log string to reference the correct recognition source for clearer debugging.

```suggestion
		log.Error().Err(detailJsonErr).Msg("Failed to parse DetailJson from AutoSellStockRedistributionOpenItemTextRecognition")
```
</issue_to_address>

### Comment 3
<location path="agent/go-service/autosell/autosell.go" line_range="222-223" />
<code_context>
+		maafocus.Print(ctx, i18n.T("autosell.check_item_price_unknown", resultItem.Text))
+	}
+
+	override := map[string]any{
+		"AutoSellStockRedistributionItemOpen": map[string]any{
+			"target": maa.Rect{
+				resultItem.Box[0],
</code_context>
<issue_to_address>
**issue (bug_risk):** Using `resultItem.Box[0..3]` without validating length risks panics on malformed OCR results.

This assumes `resultItem.Box` has at least 4 elements, but OCR JSON may yield an empty or shorter slice. Please guard this with a length check (e.g., `if len(resultItem.Box) < 4 { /* log and return */ }`) to prevent index-out-of-range panics.
</issue_to_address>

### Comment 4
<location path="agent/go-service/autosell/autosell.go" line_range="168" />
<code_context>
+type AutoSellStockRedistributionOpenItemTextAction struct{}
+
+func (a *AutoSellStockRedistributionOpenItemTextAction) Run(ctx *maa.Context, arg *maa.CustomActionArg) bool {
+	customResult, ok := arg.RecognitionDetail.Results.Best.AsCustom()
+	if !ok {
+		log.Error().Msg("Failed to get custom recognition result")
</code_context>
<issue_to_address>
**issue (bug_risk):** Assuming nested fields on `arg.RecognitionDetail` exist may cause nil dereferences.

This dereferences `arg`, `arg.RecognitionDetail`, `arg.RecognitionDetail.Results`, and `Results.Best` without nil checks. If recognition fails or the result shape changes, this will panic before `AsCustom()` is reached. Consider adding nil guards for each step and logging + returning false when the expected structure is missing.
</issue_to_address>