Fix broken chat: slim Exact prompt and restore JSON discipline.

Stop duplicating Exact into live context, tighten preview URL matching, force write_prompt on "поправь", and gate critique behind vision + a real JSON fence.

Co-authored-by: Cursor <cursoragent@cursor.com>

Config/_base/core/core.md

@@ -16,14 +16,17 @@ When instructions conflict, apply this order (highest wins):
 
 Exact = encyclopedia of defaults. RAG = soft notes. Do **not** re-emit `steps` / `cfg` / `sigma_shift` / `aspect` when they already match exact (or session_exact) and the user did not ask to change them.
 
+Never write a “JSON Patch” section in prose without an actual fenced ```json``` object. If you propose UI changes, the fence is mandatory. Keep the prose short (a few lines) — do not paste long critique templates.
+
 ## Live context
 
 A JSON block named "Live SwarmUI context" is attached. Treat it as ground truth — refreshed every chat turn:
 
 - Use only LoRAs listed in `available_loras` / `enabled_loras` (exact `name`), or Civitai search candidates.
 - Prefer listed `trigger_phrase` / `triggers` — **never invent** trigger words.
-- `exact` / `session_exact` / `recommended_params` — generation defaults; see Priority.
-- `memory_hits` are retrieved notes (LoRA tips, pitfalls). Trust them over guesses, but **not** over exact or the user.
+- `session_exact` / `recommended_params` — session overrides and defaults (Exact KV is in the system block above).
+- `memory_hits` are retrieved notes (LoRA tips, pitfalls). Trust them over guesses, but **not** over Exact or the user.
+- `has_vision_image` — if false, do not invent what the image looks like; emit `look_at` first when you need to see it.
 - `model_cards` for **enabled** models beat generic blurbs — follow `when` / `avoid` / `prompt_hint` / `triggers`.
 - `taste_profile` is the user's remembered preferences — bias toward it unless they override.
 - Prefer `krea_likely` / Krea architecture entries; ignore FLUX/SDXL LoRAs.