better-harness

# Better Harness Review the coding-agent system: context, execution, control, feedback, and learning; keep Sessions, project, and Agent assets independent. ## Step 1: Resolve Scope and Collect the Evidence Bundle Route: - `<better-harness-fix-output>`: [Finding-bound Fix](references/finding-bound-fix.md). - No callback plus leading `fix`, `repair`, or `\u4fee\u590d`: [Manual Direct Fix](references/manual-direct-fix.md). - Review/evaluation/reporting or mixed review-and-fix: Step 1. Resolve the Skill path, `<better-harness-root>` as `../..`, a supported `<node>`, and `<cli>` as `<node> <better-harness-root>/scripts/better-harness.mjs`. Stop if any owner is missing; never select another cache or runtime by search order. Resolve absolute target, decision, acceptance boundary, risks, locale (request language by default), output mode, provider, and depth. Quick uses three items and 7 days; normal uses five and 30 days. Default Qoder/Cursor to durable Canvas and other rendering hosts to HTML. Providers without REPORT_RENDERING proceed only inline or no-files and must not create HTML, Markdown, or Canvas output. Keep providers separate. Use the current one unless project-wide review explicitly authorizes multiple supported providers. Qoder project Memory title metadata is part of the selected workspace baseline. Memory bodies, Codex Memory, Qoder global Memory, user-home, raw Session, installed-plugin, marketplace, and historical-insight access require explicit scope. Before d...