All 45 log statements in actions.go used <EssenceFilter> prefixes and embedded context (rule names, step labels) directly in Msg, violating the go-service zerolog convention.

Changes

• Removed <EssenceFilter> prefix from every Msg string
• Added Str("component", "EssenceFilter") to all log calls
• Moved contextual identifiers to typed fields:
  • Rule names → Str("rule", "MatchSlot3Level3Practical") / Str("rule", "MatchFuturePromising")
  • Init steps → Str("step", "LoadMatcherConfig") / "LoadDatabase" / "LoadOptions" / "ValidatePresets" / "FilterWeapons" / "BuildSkillCombinations" (descriptive names instead of Step2–Step7)
  • Action scope → Str("action", "CheckTotal") / "RowCollect" / "RowNextItem" / "CheckItem"
• Msgs reduced to short English descriptions

Before / after example:

// Before
log.Info().
    Str("slot3_skill", matchResult.SkillsChinese[2]).
    Int("slot3_level", slot3Lv).
    Int("min_level", slot3MinLv).
    Msg("<EssenceFilter> MatchSlot3Level3Practical: 保留实用基质")

// After
log.Info().
    Str("component", "EssenceFilter").
    Str("rule", "MatchSlot3Level3Practical").
    Str("slot3_skill", matchResult.SkillsChinese[2]).
    Int("slot3_level", slot3Lv).
    Int("min_level", slot3MinLv).
    Msg("keep practical essence")

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.