build: add maplibre-gl dependency and update design docs

Add maplibre-gl v5.24.0 to project dependencies, and overhaul the agent-html TASTE.md documentation to refine design judgment guidelines, add new boundary and posture sections, and update review checklists for consistent artifact creation.

Author: Sayhi-bzb

agent-html/TASTE.md

@@ -2,15 +2,48 @@
 
 This file owns portable Canvas artifact design judgment inside distributed `agent-html`.
 
-It is not a hard-rule file, API surface, primitive catalog, or host architecture guide. `AGENTS.md` owns executable rules. Component and style routes own source selection. `TASTE.md` owns the visual and compositional judgment agents need when an artifact must feel like a coherent work surface instead of a component inventory.
+It is not a hard-rule file, style preset, API surface, primitive catalog, or
+host architecture guide. `AGENTS.md` owns executable rules. Component and style
+routes own source selection. Theme and design documents own the current subject.
+`TASTE.md` owns the portable judgment agents need when an artifact must feel
+like a coherent work surface instead of a component inventory.
 
-## Artifact Judgment
+Taste should make the next design decision cheaper, not make the final design
+more predictable.
 
-- Treat artifact content as a scene before treating it as a component list.
-- Let the primary media, object, or workflow establish the stage before adding UI containers.
-- Make one visual or object lead each major block.
-- Use UI as annotation, orientation, and control around the work; do not let UI containers become the work.
-- Prefer existing Canvas primitives and public content classes before inventing new component families.
+## Boundary
+
+- Use taste as a judgment route, not a layout recipe.
+- Reuse the judgment from prior artifacts, not their shape.
+- Treat prior artifacts as evidence, not policy.
+- Let the subject choose the form before applying a known pattern.
+- Do not turn one successful artifact into the default artifact voice.
+
+## Subject Before Pattern
+
+- Find the artifact's primary object before choosing components: scene,
+  workflow, console, route, archive, instrument, simulation, dashboard, game,
+  or another subject-native form.
+- Ask whether the artifact is meant to be watched, operated, compared,
+  inspected, played, or read.
+- Let the primary media, object, data, or workflow establish the stage before
+  adding UI containers.
+- Use UI as annotation, orientation, and control around the work; do not let UI
+  containers become the work.
+- If two unrelated subjects start producing the same block structure, stop and
+  re-find the subject.
+
+## Artifact Posture
+
+- Treat artifact content as a subject-native work surface before treating it as
+  a component list.
+- Give each major block one leading object, workflow, evidence, or decision.
+- A block does not need a hero image when a map, timeline, table, console,
+  canvas, or interaction is the real lead.
+- Prefer existing Canvas primitives and public content classes before inventing
+  new component families.
+- Add a local pattern only when it reduces repeated behavior or clarifies a
+  repeated arrangement.
 
 ## Layout Judgment
 
@@ -19,6 +52,8 @@ It is not a hard-rule file, API surface, primitive catalog, or host architecture
 - Do not wrap every image, caption, source link, and note in separate bordered surfaces.
 - Avoid card-inside-card depth unless each layer has a distinct object identity.
 - Let image-heavy artifacts use images as layout structure, not only as content inside cards.
+- If the layout starts reading as stacked containers, remove hierarchy before
+  adding more hierarchy.
 
 ## Media Judgment
 
@@ -27,22 +62,41 @@ It is not a hard-rule file, API surface, primitive catalog, or host architecture
 - Replace visually similar supporting images when they repeat the same idea.
 - Keep credits and sources traceable without interrupting the narrative rhythm.
 - Use inline image credits near media and collect long source lists in a final source area when repeated links would break the story.
+- Do not let available media redefine the subject. Use media to prove the
+  current design claim.
 
-## Component Judgment
+## Component Judgment and Variety
 
 - Use `components/ui` primitives for ordinary actions, labels, display, disclosure, overlays, and navigation.
 - Use existing rich components only when their behavior matches the task.
 - Reuse `Timeline` for chronological or route structure before making a custom route component.
 - Do not create a new rich component for a one-off artifact arrangement.
-- Promote a local pattern only when repeated behavior or a reusable arrangement appears.
+- Repeated components are acceptable only when the cognitive task repeats.
+- If several blocks use the same component shape, check whether the artifact is
+  expressing content or repeating a template.
+- Choose components by information job: control, comparison, annotation,
+  sequence, evidence, disclosure, navigation, or status.
+
+## Creativity Boundary
+
+- Taste should remove low-value defaults, not remove surprise.
+- A taste rule is suspect when it makes different subjects sound the same.
+- Avoid converting review feedback into universal form rules.
+- Preserve room for subject-specific structures that contradict prior examples.
+- When taste and subject conflict, re-check the subject before copying the
+  taste.
 
 ## Review Checklist
 
 - The first viewport identifies the artifact subject without reading the file name.
-- Each major block has one leading visual, object, or workflow.
+- Did the subject choose the structure?
+- Are we copying a previous artifact's shape?
+- Each major block has one leading object, workflow, evidence, or decision.
 - Borders are not the default hierarchy mechanism.
 - Panels mark meaningful boundaries instead of routine spacing.
 - Source links and credits are traceable without dominating the page.
 - Repeated images in the same block say different things.
+- Repeated components repeat because the task repeats, not because the template repeats.
 - Existing primitives are composed before new components are invented.
 - The artifact reads as a coherent scene or workflow, not a pile of containers.
+- The next design decision is cheaper after reading this file.