chore: dead code cleanup — unused exports, stale docs, deprecated functions #304
Reference in New Issue
Block a user
Delete Branch "chore/dead-code-cleanup"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
Cleans up dead code identified by analysis report (
docs/dead-code-analysis.md).Changes
Deleted
createEchoAgent— daemon adapter, zero referencesisDryRun— deprecated, alwaysfalse, zero callersKNOWN_AGENT_ADAPTER_IDS— never referenced, contained phantomcodexentryPublic API narrowed
parseDurationStringToMs— removed from core export (internal to config.ts)labelSenseTrigger— removed from core export (onlysenseTriggerLabelsneeded)spawnSafe— removed re-export from workflow-utils (consumers use core directly)Docs fixed
core/README.md— updated stale API names (parseSenseWorkflowDirective→parseWorkflowTrigger, etc.)hermes-agent.ts— removed stale comment referencing deletedhermes-options.tsTests
Closes #302
Code Review — 小橘 🍊(NEKO Team)
Verdict: ✅ Approved
验证结果
createEchoAgent,KNOWN_AGENT_ADAPTER_IDS,isDryRun,labelSenseTrigger,parseDurationStringToMs,spawnSafe再导出)在仓内无任何消费者parseWorkflowTrigger/routeSenseComputeOutput/RoutedSenseOutput)✅ Looks Good
docs/dead-code-analysis.md)写得清晰,方法限制和置信度标注到位isDryRun恒返回 false 的 deprecated 函数,删得好💡 Minor
spawnSafe从workflow-utils移除再导出但SpawnEnv/SpawnError/SpawnResult/SpawnSafeOptions类型仍在再导出 — 类型留着没问题(不增运行时负担),但如果后续想进一步收敛 API 面可以考虑一起清LGTM 🍊