升级Trellis并精简项目知识（09-05-trellis-upgrade-rule-cleanup）

更新Trellis适配、任务归属与归档失败恢复，精简技能入口和知识读取规则。
保留权限、证据、事务及独立复核合同；纳入对应任务及已完成复核记录。
仅本地提交，不启用新平台适配，不推送或部署。

.agents/skills/trellis-before-dev/SKILL.md

@@ -5,11 +5,9 @@ description: "Load the task and affected-layer guidelines before implementation
 
 # Before Development
 
-1. Read the current PRD and applicable design/implementation notes if not already current in context.
-2. Identify the smallest behavior gap, affected files, exclusions and validation commands. Reuse the approved plan rather than writing another checklist.
-3. Discover package indexes only when the affected layer is unknown. Read its relevant coding and quality contracts; follow references needed for this change.
-4. Read cross-layer or reuse guides only when shared contracts, multiple layers, shared constants or new abstractions are involved.
-5. Once the plan is approved, continue through implementation and relevant validation. Ask again only for material changes to scope, risk or acceptance, or separately protected operations.
-6. Keep unrelated dirty files and pre-existing failures out of scope. A local refactor requires evidence that behavior stays unchanged.
+1. Reuse the current PRD and approved plan; load missing design/implementation context. Identify the behavior gap, affected files, exclusions and meaningful checks.
+2. Locate affected-layer contracts through the package index. For large specs use `rg -n '^#{1,3} ' <file>`, then read general rules, complete relevant sections and required references. Expand for shared/cross-layer contracts; a search excerpt is not full coverage. Reuse unchanged context.
+3. Continue approved implementation and validation. Ask again only for material changes to scope, risk or acceptance, or separately protected operations.
+4. Preserve unrelated dirty files and pre-existing failures. Verify behavior for local refactors; choose checks for this change, not full business testing for rule-only edits.
 
-Do not force full document reads, repeat unchanged context, require unavailable tools, or turn a rule-only task into full business testing. Preserve privacy, production and independent-review boundaries from AGENTS.md.
+Keep privacy, production and independent-review boundaries from AGENTS.md. Use supported fallbacks for unavailable optional tools.