fix: 平台构建

AGENTS.md

@@ -20,6 +20,10 @@ The machine-side run executor lives in the independent repository `git@git.npc0.
 
 Do not place implementation code outside the matching root. Shared contracts must be generated or copied through explicit contract packages, not imported by reaching across ownership boundaries casually.
 
+## CSS Authoring Rules
+
+Any task that touches CSS must keep CSS declarations compressed and compact. Do not expand a single selector's style block across many lines when it can be written as a concise one-line rule.
+
 ## OpenSpec Rules
 
 - Use judgment before creating an OpenSpec change. Create one when the work changes behavior, architecture, public/API contracts, validation rules, persistence, security boundaries, cross-root workflows, or the required product/visual direction.
@@ -35,6 +39,12 @@ When creating a task, include the following prompt boundaries before implementat
 - Directional prompt (方向提示词): state the expected implementation direction, affected project root, relevant existing patterns to preserve, and verification command or evidence expected.
 - Boundary prompt (任务边界): explicitly list out-of-scope areas, forbidden product expansions, and files or roots that must not be touched unless the task explicitly requires them.
 
+## Git Completion Rules
+
+For every substantial session task that modifies repository files, automatically stage only the files changed for that task, create a concise git commit after verification succeeds, and push the current branch to its configured git remote before sending the final response.
+
+Do not include unrelated pre-existing worktree changes in the commit. If commit or push is blocked by missing credentials, a missing remote, conflicts, or a failing required verification step, report the blocker clearly instead of broadening the commit scope.
+
 ## Structure Rules
 
 Backend roots must keep these concerns in fixed directories: