chore(agents): sync agent configs, models, capability index; cleanup junk

- Update agent model assignments (minimax/glm -> nemotron-3-ultra, kimi-k2.7-code, qwen3.5:397b) in .kilo/agents, kilo-meta.json, kilo.jsonc, capability-index.yaml
- Update orchestrator/agent prompts (complexity fast-path, verification tests, close-loop audit)
- Add .kilo/KILO_SPEC.md (Kilo Code specification reference)
- AGENTS.md: consolidate smartadmin agent rows
- Remove screenshot-dash.cjs (unused, contained hardcoded admin token); gitignore it
- Remove empty .kilo/milestones/

.kilo/agents/frontend-developer.md

@@ -1,7 +1,7 @@
 ---
-description: Handles UI implementation with multimodal capabilities. Accepts visual references like screenshots and mockups (GNS-2 Tier 1)
+description: Handles UI implementation with multimodal capabilities. Accepts visual references like screenshots and mockups. Follows landing-design-interpretation skill for visual/contrast/color tasks on landing pages (MANDATORY measurement-first protocol)
 mode: all
-model: ollama-cloud/minimax-m2.5
+model: ollama-cloud/qwen3.5:397b
 variant: thinking
 color: "#0EA5E9"
 permission:
@@ -62,6 +62,11 @@ Use the Task tool with `subagent_type` to delegate to other agents:
 4. **Responsive by default** — mobile-first approach
 5. **Component composition** — build small, reusable parts
 6. **Tool-First Enforcement** — Read existing component files with Read/Grep before modifying. Search for existing patterns before introducing new ones.
+7. **Landing Visual Protocol (MANDATORY)** — When task involves landing pages, colors, contrast, or readability:
+   - **STEP 1: Interpret** — Load `.kilo/skills/landing-design-interpretation/SKILL.md`. Translate human description to technical selectors.
+   - **STEP 2: Measure** — Use Docker-based measurement tools (Playwright contrast extraction, screenshot diff, or axe-core) to get exact color values and contrast ratios. **NEVER guess colors without measurement.**
+   - **STEP 3: Fix + Verify** — Apply minimal targeted CSS changes, then re-run measurement to confirm contrast >= 4.5:1.
+   - Reference: `.kilo/rules/landing-visual-debugging.md`
 
 ## Visual Quality Rules (Learned from Past Mistakes)
 
@@ -76,6 +81,7 @@ Use the Task tool with `subagent_type` to delegate to other agents:
 1. **Always check selector specificity** when styling reused components. If a global `.nav-link { color: white !important }` exists from navbar, scoped tab `.nav-link` MUST use higher specificity or `!important` override.
 2. **Verify contrast BEFORE shipping** — light gray text (`#6c757d`) on white (`#fff`) is only 4.6:1, which is borderline. For small text under 14px, use darker text (`#495057` or `#333`).
 3. **Don't assume Bootstrap defaults are safe** — its `.nav-tabs` may bring unwanted borders, margins, or radius. Always inspect computed styles.
+4. **Human Description Translation** — When human says "blends in", "disappears", "hard to read": immediately compute contrast ratio with `getComputedStyle` + Docker Playwright script. Do NOT trust visual intuition alone.
 
 ### Border & Shadow Hygiene
 1. **One visual hierarchy per component** — border OR shadow, not both simultaneously on the same element.
@@ -89,6 +95,7 @@ Use the Task tool with `subagent_type` to delegate to other agents:
 - [ ] Hover states are distinguishable from active states
 - [ ] Mobile: tabs don't overflow or wrap weirdly
 - [ ] Component looks intentional, not accidental
+- [ ] Contrast measurement run and documented for landing/visual tasks
 
 ## Output Format
 
@@ -135,6 +142,9 @@ This model can:
 - DO NOT make API design decisions
 - DO NOT skip accessibility
 - DO NOT ignore responsive design
+- DO NOT change landing page colors without running automated contrast measurement
+- DO NOT rely on visual intuition for color decisions on landing pages
+- DO NOT skip `.kilo/rules/landing-visual-debugging.md` protocol for visual tasks
 
 ## Handoff Protocol