治理 Trellis spec 占位噪音与规则口径（05-29-spec-governance-cleanup）

.trellis/spec/hyb-oa/deployment-trialrun.md

@@ -15,10 +15,10 @@ operations require explicit approval and evidence.
   if the example contract drifts.
 - After deployment, report commit hash, `/ready`, public smoke results and
   whether the user can test.
-- Real business writes are manual unless an Issue explicitly authorizes a
-  controlled test write.
+- Real business writes are manual unless the current Trellis task explicitly
+  authorizes a controlled test write.
 - Do not execute real payments, import bank statements, connect payment
-  providers or write ERP without a separate approved Issue.
+  providers or write ERP without a separate approved Trellis task.
 
 ## Scenario: Deployment Env Contract
 

.trellis/spec/hyb-oa/frontend-react-vite-design.md

@@ -8,6 +8,10 @@ experience and business-boundary fact source, not a visual, brand or aesthetic
 rulebook. For PC/mobile/WeCom pages, add Playwright or visual verification when
 reasonable.
 
+This spec keeps hyb-oa-specific React/Vite, shared-component, business-boundary
+and verification contracts. Do not copy broad aesthetic guidance from
+`frontend-design` into this file; use the skill directly for design judgment.
+
 ## Rules
 
 - Use existing React/Vite/Tailwind patterns and shared components before adding
@@ -26,7 +30,7 @@ reasonable.
 ## Frozen / Boundary Items
 
 Frozen modules and Enterprise WeChat-owned HR/attendance entries must be labeled
-or hidden according to the active Issue; do not silently re-enable them.
+or hidden according to the current Trellis task; do not silently re-enable them.
 - Use the shared `WorkspaceNotice` pattern for trial boundaries, safety notes,
   and post-trial capabilities instead of page-local warning blocks.
 - Trial-facing PC lists must hide obvious TEST/SMOKE records by default when a

.trellis/spec/hyb-oa/reimbursement-invoice-ocr.md

@@ -8,9 +8,9 @@ duplicate detection or attachment behavior.
 ## Rules
 
 - PDF invoice OCR is the maintained main path.
-- Image OCR remains frozen unless a later Issue explicitly reopens it.
+- Image OCR remains frozen unless a later Trellis task explicitly reopens it.
 - Do not write raw invoice images, sensitive form values or full OCR payloads to
   repo docs, Issue CSV, Trellis task files or chat.
 - Reimbursement flow tests should cover upload/OCR, duplicate handling,
   submission, approval, payment batch, receipt attachment and AP export when the
-  Issue scope touches those areas.
+  Trellis task scope touches those areas.