docs(constitution): harness button placement standardization rule for CRUD and batch processing

AGENTS.md

@@ -94,6 +94,11 @@ All work in this repository MUST follow `docs/CURRENT/WBS_EXECUTION_PROCEDURES.m
 - J39 and every new schedule remain disabled until their source, calendar, ownership and alert contracts are approved.
 - Never claim .NET, pnpm, PostgreSQL, Playwright or Shadow evidence passed unless the actual artifact is attached.
 - **[CRITICAL IRON RULE] Viewport-Fit Zero-Scroll Layout**: Except for analytical dashboards, ALL workstation screens MUST fit 100% within the initial viewport upon loading WITHOUT page-level window scrolling. All primary grids, forms, and control panels must automatically calculate `height: calc(100vh - header/tabs)` and handle internal scrolling inside containers.
+- **[CRITICAL IRON RULE] Standardized Button Layout Strategy**:
+  1. **Page Action Toolbar (Top-Right `.ks-page__actions`)**: Dedicated exclusively to **Primary Processing Actions** (e.g., `▶ 배치 실행`, `⚡ 리밸런싱 실행`, `📤 데이터 수집`) and **Global Page Operations** (e.g., `➕ 신규 등록`). Secondary actions are styled as outline/ghost.
+  2. **Grid Row & Item Context Actions (Table Row Actions)**: Dedicated to **Single-Row CRUD & Processing** (e.g., `✏️ 수정`, `🗑️ 삭제`, `🔍 상세보기`, `▶ 재처리`). Placed in a pinned right column or explicit context menu; never placed in page top toolbar.
+  3. **Multi-Selection Batch Toolbar (Grid Top/Bottom Selection Bar)**: Activated conditionally upon multi-row selection for **Bulk Actions** (e.g., `선택 일괄 승인(3)`, `선택 일괄 삭제`).
+  4. **Form & Dialog Footer Toolbar (Form Bottom Action Bar)**: Dedicated to **Form Submission & Dialog Operations** (Right-aligned: `[취소 (Secondary)] [저장/확인 (Primary)]`).
 
 ## v16.0 Gitea API & CI/CD Automation
 
@@ -353,11 +358,13 @@ Every task — code change, refactor, new feature, tooling, infrastructure — m
 - [ ] **Right Way:** Shortcut (--no-verify, force) 안 썼는가? 근본 해결했는가?
 - [ ] **Debt:** 새로운 debt 만들지 않는가? 기존 debt 감축하는가?
 - [ ] **Viewport Fit (UI):** 대시보드를 제외한 모든 업무 화면이 페이지 스크롤 없이 초기 로딩 시 100% 한눈에 들어오는가?
+- [ ] **Button Standard (UI):** 상단 툴바(배치/등록), 행별 작업(수정/상세), 다중선택(일괄), 폼 푸터(취소/저장) 버튼 배치가 규칙 매트릭스를 따르는가?
 
 ### Anti-Patterns (금지)
 
 - ❌ "일단 만들고 나중에 리팩터" → Feature 초기부터 정공법
 - ❌ "페이지에 창 스크롤바가 생기게 방치" → 대시보드 제외 모든 업무 화면은 Viewport-Fit Zero-Scroll 필수
+- ❌ "버튼 위치 난잡 배치" → 상단 우측(페이지/배치), 행 내부(개별 CRUD), 선택바(일괄), 폼 푸터(저장/취소) 표준 무시 금지
 - ❌ "혹시 필요할까봐 추상화" → Necessity-driven만
 - ❌ SELECT * / Generic Repository → Explicit columns, explicit logic
 - ❌ "이건 작은 변경이라 테스트 스킵" → 모든 경로 characterize