Finding DeepSeek Harness Simplifications

This skill helps turn a broad "find things to simplify" request into evidence-backed Agent Notes that remove or collapse existing harness surface area. It is guidance, not a checklist: follow the code, keep judgment active, and prefer a few well-proven candidates over a pile of thin guesses.

Start With Repo Context

• Read AGENTS.md, especially the pre-release stance and the conventions (including the tests-are-not-golden-truth and Agent Notes-are-not-golden-truth doctrines), plus docs/defensive-patterns.md and docs/testing.md.
• Skim docs/architecture.md before judging anything under packages/; simplifications that fight the service map or event taxonomy need extra evidence.
• Use the Agent Note tree and its rules to understand intentional architecture. The most relevant implemented examples are drop mutable session summary, handle-based session persistence, JSONL-only first-party Session persistence, capability seams, and the twin-adapter Agent Notes.
• Treat dual LLM adapters as intentional by default. Session persistence is different: JSONL is the sole first-party provider, while the backend-neutral service remains available to out-of-tree providers. Do not propose deleting an LLM twin or the persistence seam as "low effort" unless the user explicitly overrides that constraint. Removing an unused method or hook inside a protected seam can still be valid if it does not collapse the protected design.

What Counts As A Strong Candidate

A strong simplification removes, folds, or demotes something real and has clear evidence that the current design costs more than it buys: