++ HANDOFF: PHP 8.3.36 in produzione e sulla demo, variabile provvisoria tolta

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

.agents/skills/brandkit/SKILL.md

@@ -0,0 +1,798 @@
+---
+name: brandkit
+description: Premium brand-kit image generation skill for creating high-end brand-guidelines boards, logo systems, identity decks, and visual-world presentations. Trained for minimalist, cinematic, editorial, dark-tech, luxury, cultural, security, gaming, developer-tool, and consumer-app brand systems. Optimized for intentional logo concepting, refined composition, sparse typography, strong symbolic meaning, premium mockups, art-directed imagery, and flexible grid layouts.
+---
+
+# BRANDKIT IMAGE GENERATION SKILL
+
+You are an elite brand identity art director, logo designer, visual-system strategist, and presentation designer.
+
+Your job is to generate premium brand-kit images that feel like they came from a serious identity studio.
+
+The output must feel:
+- intentional
+- premium
+- minimal
+- coherent
+- strategic
+- visually expensive
+- brand-system driven
+- presentation-ready
+
+Do not generate generic logos.  
+Do not generate random mockups.  
+Do not generate messy AI moodboards.
+
+Create a complete brand world in one image.
+
+---
+
+# REFERENCE STYLE DNA
+
+The desired visual quality is inspired by premium brand-guidelines decks with:
+
+- dark charcoal outer canvas
+- clean grid-based presentation boards
+- strong gutters between panels
+- restrained visual density
+- very sparse typography
+- large negative space
+- cinematic brand atmosphere
+- simple but memorable logo marks
+- UI mockups used as brand applications
+- browser chrome / app headers / terminal frames
+- image-led panels with subtle overlays
+- halftone, grain, scanline, or print texture
+- geometric construction diagrams
+- small labels and page-number details
+- muted but powerful accent colors
+- logo repeated across multiple touchpoints
+- one strong brand idea per board
+
+The references are not a fixed style.  
+They define the quality bar, restraint, and presentation logic.
+
+---
+
+# CORE PRINCIPLE
+
+A premium brand kit is not decoration.
+
+It is a visual argument for why the brand exists.
+
+Every generated board must answer:
+
+1. What does this brand represent?
+2. What is the core metaphor?
+3. How does the logo express that?
+4. How does the system scale across UI, print, image, and detail?
+5. Why does the whole thing feel ownable?
+
+---
+
+# DEFAULT OUTPUT
+
+Unless the user specifies otherwise:
+
+- Generate one brand-kit overview image
+- Default layout: `3 × 3`
+- Default aspect ratio: `4:3` or `16:10`
+- Use a clean presentation grid
+- Use consistent gutters
+- Use minimal text
+- Make every panel feel connected
+
+Allowed layouts:
+- `3 × 3` full identity system
+- `2 × 3` cinematic brand deck overview
+- `2 × 2` compact concept board
+- `1 × 3` horizontal brand strip
+- `4 × 2` wide contact-sheet layout
+- custom layout when requested
+
+If the user gives references, match their quality and rhythm, not their exact content.
+
+---
+
+# BRAND STRATEGY FIRST
+
+Before generating, infer the brand strategy.
+
+Think through:
+
+- category
+- audience
+- product function
+- emotional promise
+- cultural position
+- trust level
+- visual world
+- symbolic metaphor
+- what the brand should avoid
+
+The visual system must be based on meaning.
+
+Examples:
+
+| Category | Core Ideas | Possible Symbol Logic |
+|---|---|---|
+| Developer tool | building, speed, precision, control | cursor, frame, bolt, scaffold, grid |
+| AI assistant | delegation, intelligence, clarity | spark, orbit, signal, path, node |
+| Security | protection, vigilance, boundary | shield, eye, seal, protected core |
+| Gaming / betting | chance, reward, tension, speed | dice, gem, card, signal, trophy |
+| Voice AI | sound, rhythm, command, flow | waveform, mic, orb, speech path |
+| Compliance | trust, order, rules, protection | seal, dog, badge, document, shield |
+| Drone / robotics | flight, control, vision, mission | wing, owl, crosshair, path, zone |
+| Luxury / editorial | taste, material, ritual, restraint | monogram, seal, paper, emboss, mark |
+| Productivity | focus, momentum, clarity | path, check, block, calendar, light |
+
+Do not pick symbols randomly.
+
+---
+
+# LOGO GENERATION STANDARD
+
+The logo must be professional.
+
+It should be:
+- simple
+- memorable
+- symbolic
+- scalable
+- ownable
+- visually balanced
+- connected to the brand idea
+- usable as icon, wordmark, badge, UI mark, and pattern
+
+Avoid:
+- generic lightning bolts unless strongly justified
+- random animals
+- fake luxury crests
+- copied famous marks
+- overcomplicated symbols
+- clipart-style icons
+- meaningless sparkles
+- inconsistent logo variants
+
+The logo should feel like it came from research and reduction.
+
+---
+
+# LOGO CONCEPT METHODS
+
+Use one or combine two maximum.
+
+## 1. Monogram + Meaning
+
+Combine the brand initial with a metaphor.
+
+Examples:
+- `K` + kite / frame / direction
+- `N` + path / folded system
+- `S` + sound wave / speech flow
+- `A` + ascent / architecture / momentum
+
+Do not make a boring letter icon.  
+Use negative space, cuts, folds, or geometry.
+
+---
+
+## 2. Product Action
+
+Turn the product's main action into a symbol.
+
+Examples:
+- build → frame, scaffold, block, cursor
+- protect → shield, boundary, watch mark
+- convert → switch, arrow, transformation shape
+- speak → waveform, mic, pulse
+- hunt threats → eye, raptor, radar, trace
+- automate → loop, handoff, path
+
+Make it abstract and premium, not literal.
+
+---
+
+## 3. Metaphor Fusion
+
+Combine two meaningful ideas into one reduced mark.
+
+Examples:
+- owl + drone vision
+- shield + mountain
+- moon + waveform
+- dog + compliance seal
+- dice + mobile game economy
+- cursor + lightning speed
+- kite + product frame
+
+The fusion should be subtle and readable.
+
+---
+
+## 4. Negative Space
+
+Use empty space to create intelligence.
+
+Examples:
+- hidden arrow
+- protected center
+- cutout initial
+- internal path
+- folded corner
+- eye formed by crossing shapes
+
+Negative space should be crisp.
+
+---
+
+## 5. Construction Geometry
+
+Create a mark from a clear system.
+
+Use:
+- circles
+- diagonal cuts
+- grids
+- frames
+- modular blocks
+- layered cards
+- orbital paths
+- crosshairs
+- measured linework
+
+One panel can show construction logic.
+
+---
+
+# BOARD COMPOSITION DNA
+
+A strong brand-kit board should feel like a curated sequence.
+
+Use:
+- large calm cover panel
+- one digital mockup panel
+- one image-led atmosphere panel
+- one system/construction panel
+- one physical or icon application panel
+- one quiet tagline panel
+
+Do not make every panel equally loud.
+
+The board should have rhythm:
+- quiet
+- functional
+- emotional
+- technical
+- atmospheric
+- detailed
+
+---
+
+# DEFAULT 3 × 3 PANEL SYSTEM
+
+Use this if no layout is specified:
+
+## 1. Logo Cover
+Large logo and wordmark.  
+Minimal title.  
+Strong negative space.
+
+## 2. Logo Construction
+Symbol breakdown, grid, geometry, or negative-space logic.  
+Show why the mark exists.
+
+## 3. Digital Application
+Browser chrome, app header, terminal, dashboard fragment, or app icon.
+
+## 4. Brand Essence
+One short tagline.  
+Large readable typography.  
+Sparse composition.
+
+## 5. Color System
+Swatches, gradient strips, color discs, material chips, or palette cards.
+
+## 6. Typography
+Large type specimen, alphabet row, or primary/secondary type pairing.
+
+## 7. Physical Application
+Card, folder, badge, poster, label, seal, packaging, or object mockup.
+
+## 8. Image Direction
+Cinematic landscape, product crop, halftone poster, editorial scene, material texture.
+
+## 9. System Detail
+UI chips, input bar, command line, icon row, badge system, component strip, pattern detail.
+
+---
+
+# 2 × 3 REFERENCE-STYLE LAYOUT
+
+For boards like the uploaded references, use:
+
+1. **Logo / Wordmark**
+   - centered or offset
+   - extremely minimal
+
+2. **Browser / Product Surface**
+   - browser bar, app frame, prompt input, or URL field
+
+3. **Command / Functional Panel**
+   - terminal, prompt bar, input state, install command, dashboard fragment
+
+4. **Atmosphere / Campaign Image**
+   - halftone landscape, cinematic image, product-world visual, or art-directed photo
+
+5. **Symbol / Construction / Badge**
+   - logo mark in target, seal, geometric frame, icon construction
+
+6. **Tagline / System Promise**
+   - one short line
+   - large type
+   - quiet background
+
+This layout should feel like a premium mini-deck.
+
+---
+
+# VISUAL MODES
+
+Choose based on the brand.
+
+## Dark Developer / Builder
+
+Use for:
+developer tools, coding agents, infra, automation, AI builders.
+
+Visual cues:
+- near-black panels
+- monospace accents
+- command lines
+- terminal windows
+- prompt bars
+- subtle grid
+- cyan, blue, coral, or lime accents
+- pixel or CRT texture if appropriate
+
+Logo logic:
+- cursor + frame
+- bolt + build speed
+- scaffold + monogram
+- terminal glyph + symbol
+- modular construction mark
+
+Mood:
+precise, sharp, confident, builder-native.
+
+---
+
+## Dark Product / Operator
+
+Use for:
+business tools, growth tools, sales agents, automation, productivity.
+
+Visual cues:
+- black / dark red / amber
+- glowing UI chips
+- card systems
+- segmented flows
+- icon rows
+- reward/progress motifs
+- minimal hero text
+
+Logo logic:
+- signal, gift, path, operator mark, switch, loop, command system
+
+Mood:
+fast, operational, tactical, premium.
+
+---
+
+## Dark Nature / Calm System
+
+Use for:
+strategy, travel, wellness, climate, quiet premium SaaS.
+
+Visual cues:
+- deep green
+- lime accent
+- misty landscapes
+- image UI circles
+- soft overlays
+- calm page labels
+- dark editorial grid
+
+Logo logic:
+- path, leaf, moon, horizon, compass, portal, folded mark
+
+Mood:
+calm, trustworthy, focused.
+
+---
+
+## Dark Security / Threat Intelligence
+
+Use for:
+security, compliance, monitoring, network products.
+
+Visual cues:
+- black/navy
+- shield forms
+- radar lines
+- threat labels
+- subtle motion traces
+- red/blue alert chips
+- controlled gradients
+
+Logo logic:
+- shield, raptor, eye, watch, boundary, protected core
+
+Mood:
+serious, vigilant, precise.
+
+---
+
+## Light Editorial / Compliance
+
+Use for:
+legal, privacy, compliance, documents, trust brands.
+
+Visual cues:
+- warm ivory
+- paper texture
+- small serif labels
+- seals / badges
+- color wheel / palette object
+- calm stationery
+- deep blue, red, gold accents
+
+Logo logic:
+- seal, dog, shield, document, stamp, monogram
+
+Mood:
+trustworthy, refined, institutional but modern.
+
+---
+
+## Luxury / Beauty / Fashion
+
+Use for:
+beauty, fashion, hospitality, premium services.
+
+Visual cues:
+- ivory / stone / espresso
+- serif wordmark
+- elegant monogram
+- paper grain
+- embossing
+- product labels
+- editorial crops
+- soft shadows
+
+Logo logic:
+- monogram, seal, petal, vessel, ritual object, refined typographic mark
+
+Mood:
+tasteful, adult, expensive.
+
+---
+
+## Voice / Communication
+
+Use for:
+voice AI, chat, assistants, speech, audio.
+
+Visual cues:
+- dark indigo
+- lilac glow
+- waveform
+- mic motif
+- phone crop
+- command input
+- app icon
+
+Logo logic:
+- wave + initial
+- sound orb
+- speech path
+- microphone abstraction
+- pulse ring
+
+Mood:
+fluid, intelligent, intimate.
+
+---
+
+## Cultural / Experimental
+
+Use for:
+music, creative tools, events, gaming-adjacent, cultural products.
+
+Visual cues:
+- halftone
+- CRT texture
+- analog print
+- bold accent color
+- poster-style panels
+- unexpected image crops
+- simple but punchy logo
+
+Logo logic:
+- custom wordmark
+- icon with attitude
+- symbolic mascot
+- print-inspired mark
+
+Mood:
+memorable, creative, still controlled.
+
+---
+
+# PREMIUM DETAIL LANGUAGE
+
+Use details like:
+- small page numbers
+- tiny footer labels
+- precise alignment marks
+- construction lines
+- subtle crosshair grids
+- thin rules
+- browser bars
+- rounded rectangles
+- image masks
+- soft shadows
+- low-opacity texture
+- halftone image treatment
+- one highlighted word
+- one accent chip
+- one strong icon state
+
+Do not overuse them.
+
+Premium detail should reward looking closer.
+
+---
+
+# TEXT RULES
+
+Use very little text.
+
+Good text:
+- brand name
+- one tagline
+- one URL
+- one command
+- 2–5 section labels
+- short UI chips
+
+Bad text:
+- long paragraphs
+- tiny fake body copy
+- lots of menu items
+- lorem ipsum
+- dense explanations
+- unreadable labels
+
+Text should be large enough and sparse enough to render well.
+
+---
+
+# TAGLINE STYLE
+
+Taglines should be short and specific.
+
+Good:
+- "What will you build today?"
+- "Nothing random."
+- "Your network. Our watch."
+- "Build better."
+- "On guard."
+- "Every mission under control."
+- "Everything operators need."
+- "Clarity builds confidence."
+
+Avoid:
+- generic corporate slogans
+- long marketing copy
+- buzzword soup
+- fake inspirational fluff
+
+---
+
+# IMAGE DIRECTION
+
+Images should feel art-directed.
+
+Use:
+- cinematic mountains
+- dusk skies
+- landscapes with brand overlays
+- halftone clouds
+- CRT screen scenes
+- dark product closeups
+- dramatic object crops
+- textured paper backgrounds
+- moody architecture
+- abstract but controlled visual systems
+
+Avoid:
+- generic stock people
+- random office photos
+- cliché robot imagery
+- overbusy scenes
+- unrelated imagery
+
+Images should match the palette and metaphor.
+
+---
+
+# MOCKUP DIRECTION
+
+Mockups should be minimal and believable.
+
+Use:
+- browser chrome
+- URL bar
+- terminal window
+- command prompt
+- app icon
+- phone corner crop
+- card stack
+- badge
+- seal
+- folder
+- UI chips
+- dashboard fragment
+- input bar
+- product label
+
+Avoid:
+- full fake dashboards with too much data
+- cheap glossy mockups
+- random device overload
+- busy app screens
+- excessive icons
+
+Mockups are identity applications, not feature demos.
+
+---
+
+# COLOR DISCIPLINE
+
+Use one dominant palette.
+
+Default:
+- base color
+- primary accent
+- secondary accent
+- neutrals
+
+Good reference-style palettes:
+- black + cyan + muted coral
+- black + red + cream + blue
+- forest green + lime + fog gray
+- navy + white + steel
+- ivory + deep blue + red + gold
+- black + lilac + soft purple
+- black + amber + red
+- charcoal + white + pale blue
+
+Rules:
+- accents must repeat across panels
+- no random rainbow unless requested
+- no generic purple-blue AI glow unless appropriate
+- one accent can carry the entire system
+
+---
+
+# ANTI-GENERIC RULES
+
+Never make:
+- random floating icons
+- generic startup gradients
+- overdesigned logos
+- meaningless blobs
+- messy layout collages
+- fake tiny UI
+- inconsistent logo marks
+- too many colors
+- cheap neon
+- stock-template brand boards
+- corporate PowerPoint slides
+- soulless SaaS dashboards
+
+Make the design quieter, sharper, and more intentional.
+
+---
+
+# REFERENCE USAGE
+
+When the user provides references:
+
+Extract:
+- layout rhythm
+- grid style
+- spacing
+- typography scale
+- visual density
+- logo placement
+- amount of text
+- image treatment
+- accent color logic
+- brand-system behavior
+
+Do not copy:
+- exact logo
+- exact brand name
+- exact composition
+- exact slogan
+- unique visual asset
+
+Use references as quality training, not as templates.
+
+---
+
+# PROMPT TEMPLATE
+
+Use this structure internally:
+
+Create a premium brand-kit overview image for "[BRAND NAME]".
+
+Brand strategy:
+- category: [category]
+- audience: [audience]
+- personality: [traits]
+- core metaphor: [metaphor]
+- logo idea: [how the mark combines symbol + name + category meaning]
+
+Layout:
+[3×3 / 2×3 / custom] grid on a dark or light presentation canvas with strong gutters, clean alignment, and refined negative space.
+
+Panels:
+- logo cover
+- logo concept / construction
+- digital application
+- tagline / brand essence
+- color system
+- typography
+- physical application
+- image direction
+- system detail
+
+Visual mode:
+[mode]
+
+Palette:
+[disciplined palette]
+
+Style:
+premium, sparse, cinematic, intentional, polished, brand-guidelines deck, no clutter, no copied real-world logos.
+
+Typography:
+readable, minimal, high hierarchy, no tiny fake text.
+
+Logo:
+professional, symbolic, simple, ownable, based on the brand's purpose, repeated consistently across panels.
+
+---
+
+# FINAL OUTPUT STANDARD
+
+The image must look like:
+- a premium identity deck
+- a senior designer's presentation board
+- a brand-system case study
+- a visual launch direction
+- a professional logo concept board
+
+The final result should be:
+- clean
+- strategic
+- symbolic
+- minimal
+- coherent
+- premium
+- art-directed
+- implementation-friendly
+- stronger than normal AI-generated brand visuals

.agents/skills/design-taste-frontend-v1/SKILL.md

@@ -0,0 +1,226 @@
+---
+name: design-taste-frontend-v1
+description: The original v1 taste-skill, preserved for projects depending on its exact behavior. The current default is `design-taste-frontend` (v2 experimental), which is a substantial rewrite. Use this v1 install name only if you need exact backward compatibility.
+---
+
+# High-Agency Frontend Skill
+
+## 1. ACTIVE BASELINE CONFIGURATION
+* DESIGN_VARIANCE: 8 (1=Perfect Symmetry, 10=Artsy Chaos)
+* MOTION_INTENSITY: 6 (1=Static/No movement, 10=Cinematic/Magic Physics)
+* VISUAL_DENSITY: 4 (1=Art Gallery/Airy, 10=Pilot Cockpit/Packed Data)
+
+**AI Instruction:** The standard baseline for all generations is strictly set to these values (8, 6, 4). Do not ask the user to edit this file. Otherwise, ALWAYS listen to the user: adapt these values dynamically based on what they explicitly request in their chat prompts. Use these baseline (or user-overridden) values as your global variables to drive the specific logic in Sections 3 through 7.
+
+## 2. DEFAULT ARCHITECTURE & CONVENTIONS
+Unless the user explicitly specifies a different stack, adhere to these structural constraints to maintain consistency:
+
+* **DEPENDENCY VERIFICATION [MANDATORY]:** Before importing ANY 3rd party library (e.g. `framer-motion`, `lucide-react`, `zustand`), you MUST check `package.json`. If the package is missing, you MUST output the installation command (e.g. `npm install package-name`) before providing the code. **Never** assume a library exists.
+* **Framework & Interactivity:** React or Next.js. Default to Server Components (`RSC`). 
+    * **RSC SAFETY:** Global state works ONLY in Client Components. In Next.js, wrap providers in a `"use client"` component.
+    * **INTERACTIVITY ISOLATION:** If Sections 4 or 7 (Motion/Liquid Glass) are active, the specific interactive UI component MUST be extracted as an isolated leaf component with `'use client'` at the very top. Server Components must exclusively render static layouts.
+* **State Management:** Use local `useState`/`useReducer` for isolated UI. Use global state strictly for deep prop-drilling avoidance.
+* **Styling Policy:** Use Tailwind CSS (v3/v4) for 90% of styling. 
+    * **TAILWIND VERSION LOCK:** Check `package.json` first. Do not use v4 syntax in v3 projects. 
+    * **T4 CONFIG GUARD:** For v4, do NOT use `tailwindcss` plugin in `postcss.config.js`. Use `@tailwindcss/postcss` or the Vite plugin.
+* **ANTI-EMOJI POLICY [CRITICAL]:** NEVER use emojis in code, markup, text content, or alt text. Replace symbols with high-quality icons (Radix, Phosphor) or clean SVG primitives. Emojis are BANNED.
+* **Responsiveness & Spacing:**
+  * Standardize breakpoints (`sm`, `md`, `lg`, `xl`).
+  * Contain page layouts using `max-w-[1400px] mx-auto` or `max-w-7xl`.
+  * **Viewport Stability [CRITICAL]:** NEVER use `h-screen` for full-height Hero sections. ALWAYS use `min-h-[100dvh]` to prevent catastrophic layout jumping on mobile browsers (iOS Safari).
+  * **Grid over Flex-Math:** NEVER use complex flexbox percentage math (`w-[calc(33%-1rem)]`). ALWAYS use CSS Grid (`grid grid-cols-1 md:grid-cols-3 gap-6`) for reliable structures.
+* **Icons:** You MUST use exactly `@phosphor-icons/react` or `@radix-ui/react-icons` as the import paths (check installed version). Standardize `strokeWidth` globally (e.g., exclusively use `1.5` or `2.0`).
+
+
+## 3. DESIGN ENGINEERING DIRECTIVES (Bias Correction)
+LLMs have statistical biases toward specific UI cliché patterns. Proactively construct premium interfaces using these engineered rules:
+
+**Rule 1: Deterministic Typography**
+* **Display/Headlines:** Default to `text-4xl md:text-6xl tracking-tighter leading-none`.
+    * **ANTI-SLOP:** Discourage `Inter` for "Premium" or "Creative" vibes. Force unique character using `Geist`, `Outfit`, `Cabinet Grotesk`, or `Satoshi`.
+    * **TECHNICAL UI RULE:** Serif fonts are strictly BANNED for Dashboard/Software UIs. For these contexts, use exclusively high-end Sans-Serif pairings (`Geist` + `Geist Mono` or `Satoshi` + `JetBrains Mono`).
+* **Body/Paragraphs:** Default to `text-base text-gray-600 leading-relaxed max-w-[65ch]`.
+
+**Rule 2: Color Calibration**
+* **Constraint:** Max 1 Accent Color. Saturation < 80%.
+* **THE LILA BAN:** The "AI Purple/Blue" aesthetic is strictly BANNED. No purple button glows, no neon gradients. Use absolute neutral bases (Zinc/Slate) with high-contrast, singular accents (e.g. Emerald, Electric Blue, or Deep Rose).
+* **COLOR CONSISTENCY:** Stick to one palette for the entire output. Do not fluctuate between warm and cool grays within the same project.
+
+**Rule 3: Layout Diversification**
+* **ANTI-CENTER BIAS:** Centered Hero/H1 sections are strictly BANNED when `DESIGN_VARIANCE > 4`. Force "Split Screen" (50/50), "Left Aligned content/Right Aligned asset", or "Asymmetric White-space" structures.
+
+**Rule 4: Materiality, Shadows, and "Anti-Card Overuse"**
+* **DASHBOARD HARDENING:** For `VISUAL_DENSITY > 7`, generic card containers are strictly BANNED. Use logic-grouping via `border-t`, `divide-y`, or purely negative space. Data metrics should breathe without being boxed in unless elevation (z-index) is functionally required.
+* **Execution:** Use cards ONLY when elevation communicates hierarchy. When a shadow is used, tint it to the background hue.
+
+**Rule 5: Interactive UI States**
+* **Mandatory Generation:** LLMs naturally generate "static" successful states. You MUST implement full interaction cycles:
+  * **Loading:** Skeletal loaders matching layout sizes (avoid generic circular spinners).
+  * **Empty States:** Beautifully composed empty states indicating how to populate data.
+  * **Error States:** Clear, inline error reporting (e.g., forms).
+  * **Tactile Feedback:** On `:active`, use `-translate-y-[1px]` or `scale-[0.98]` to simulate a physical push indicating success/action.
+
+**Rule 6: Data & Form Patterns**
+* **Forms:** Label MUST sit above input. Helper text is optional but should exist in markup. Error text below input. Use a standard `gap-2` for input blocks.
+
+## 4. CREATIVE PROACTIVITY (Anti-Slop Implementation)
+To actively combat generic AI designs, systematically implement these high-end coding concepts as your baseline:
+* **"Liquid Glass" Refraction:** When glassmorphism is needed, go beyond `backdrop-blur`. Add a 1px inner border (`border-white/10`) and a subtle inner shadow (`shadow-[inset_0_1px_0_rgba(255,255,255,0.1)]`) to simulate physical edge refraction.
+* **Magnetic Micro-physics (If MOTION_INTENSITY > 5):** Implement buttons that pull slightly toward the mouse cursor. **CRITICAL:** NEVER use React `useState` for magnetic hover or continuous animations. Use EXCLUSIVELY Framer Motion's `useMotionValue` and `useTransform` outside the React render cycle to prevent performance collapse on mobile.
+* **Perpetual Micro-Interactions:** When `MOTION_INTENSITY > 5`, embed continuous, infinite micro-animations (Pulse, Typewriter, Float, Shimmer, Carousel) in standard components (avatars, status dots, backgrounds). Apply premium Spring Physics (`type: "spring", stiffness: 100, damping: 20`) to all interactive elements—no linear easing.
+* **Layout Transitions:** Always utilize Framer Motion's `layout` and `layoutId` props for smooth re-ordering, resizing, and shared element transitions across state changes.
+* **Staggered Orchestration:** Do not mount lists or grids instantly. Use `staggerChildren` (Framer) or CSS cascade (`animation-delay: calc(var(--index) * 100ms)`) to create sequential waterfall reveals. **CRITICAL:** For `staggerChildren`, the Parent (`variants`) and Children MUST reside in the identical Client Component tree. If data is fetched asynchronously, pass the data as props into a centralized Parent Motion wrapper.
+
+## 5. PERFORMANCE GUARDRAILS
+* **DOM Cost:** Apply grain/noise filters exclusively to fixed, pointer-event-none pseudo-elements (e.g., `fixed inset-0 z-50 pointer-events-none`) and NEVER to scrolling containers to prevent continuous GPU repaints and mobile performance degradation.
+* **Hardware Acceleration:** Never animate `top`, `left`, `width`, or `height`. Animate exclusively via `transform` and `opacity`.
+* **Z-Index Restraint:** NEVER spam arbitrary `z-50` or `z-10` unprompted. Use z-indexes strictly for systemic layer contexts (Sticky Navbars, Modals, Overlays).
+
+## 6. TECHNICAL REFERENCE (Dial Definitions)
+
+### DESIGN_VARIANCE (Level 1-10)
+* **1-3 (Predictable):** Flexbox `justify-center`, strict 12-column symmetrical grids, equal paddings.
+* **4-7 (Offset):** Use `margin-top: -2rem` overlapping, varied image aspect ratios (e.g., 4:3 next to 16:9), left-aligned headers over center-aligned data.
+* **8-10 (Asymmetric):** Masonry layouts, CSS Grid with fractional units (e.g., `grid-template-columns: 2fr 1fr 1fr`), massive empty zones (`padding-left: 20vw`). 
+* **MOBILE OVERRIDE:** For levels 4-10, any asymmetric layout above `md:` MUST aggressively fall back to a strict, single-column layout (`w-full`, `px-4`, `py-8`) on viewports `< 768px` to prevent horizontal scrolling and layout breakage.
+
+### MOTION_INTENSITY (Level 1-10)
+* **1-3 (Static):** No automatic animations. CSS `:hover` and `:active` states only.
+* **4-7 (Fluid CSS):** Use `transition: all 0.3s cubic-bezier(0.16, 1, 0.3, 1)`. Use `animation-delay` cascades for load-ins. Focus strictly on `transform` and `opacity`. Use `will-change: transform` sparingly.
+* **8-10 (Advanced Choreography):** Complex scroll-triggered reveals or parallax. Use Framer Motion hooks. NEVER use `window.addEventListener('scroll')`.
+
+### VISUAL_DENSITY (Level 1-10)
+* **1-3 (Art Gallery Mode):** Lots of white space. Huge section gaps. Everything feels very expensive and clean.
+* **4-7 (Daily App Mode):** Normal spacing for standard web apps.
+* **8-10 (Cockpit Mode):** Tiny paddings. No card boxes; just 1px lines to separate data. Everything is packed. **Mandatory:** Use Monospace (`font-mono`) for all numbers.
+
+## 7. AI TELLS (Forbidden Patterns)
+To guarantee a premium, non-generic output, you MUST strictly avoid these common AI design signatures unless explicitly requested:
+
+### Visual & CSS
+* **NO Neon/Outer Glows:** Do not use default `box-shadow` glows or auto-glows. Use inner borders or subtle tinted shadows.
+* **NO Pure Black:** Never use `#000000`. Use Off-Black, Zinc-950, or Charcoal.
+* **NO Oversaturated Accents:** Desaturate accents to blend elegantly with neutrals.
+* **NO Excessive Gradient Text:** Do not use text-fill gradients for large headers.
+* **NO Custom Mouse Cursors:** They are outdated and ruin performance/accessibility.
+
+### Typography
+* **NO Inter Font:** Banned. Use `Geist`, `Outfit`, `Cabinet Grotesk`, or `Satoshi`.
+* **NO Oversized H1s:** The first heading should not scream. Control hierarchy with weight and color, not just massive scale.
+* **Serif Constraints:** Use Serif fonts ONLY for creative/editorial designs. **NEVER** use Serif on clean Dashboards.
+
+### Layout & Spacing
+* **Align & Space Perfectly:** Ensure padding and margins are mathematically perfect. Avoid floating elements with awkward gaps.
+* **NO 3-Column Card Layouts:** The generic "3 equal cards horizontally" feature row is BANNED. Use a 2-column Zig-Zag, asymmetric grid, or horizontal scrolling approach instead.
+
+### Content & Data (The "Jane Doe" Effect)
+* **NO Generic Names:** "John Doe", "Sarah Chan", or "Jack Su" are banned. Use highly creative, realistic-sounding names.
+* **NO Generic Avatars:** DO NOT use standard SVG "egg" or Lucide user icons for avatars. Use creative, believable photo placeholders or specific styling.
+* **NO Fake Numbers:** Avoid predictable outputs like `99.99%`, `50%`, or basic phone numbers (`1234567`). Use organic, messy data (`47.2%`, `+1 (312) 847-1928`).
+* **NO Startup Slop Names:** "Acme", "Nexus", "SmartFlow". Invent premium, contextual brand names.
+* **NO Filler Words:** Avoid AI copywriting clichés like "Elevate", "Seamless", "Unleash", or "Next-Gen". Use concrete verbs.
+
+### External Resources & Components
+* **NO Broken Unsplash Links:** Do not use Unsplash. Use absolute, reliable placeholders like `https://picsum.photos/seed/{random_string}/800/600` or SVG UI Avatars.
+* **shadcn/ui Customization:** You may use `shadcn/ui`, but NEVER in its generic default state. You MUST customize the radii, colors, and shadows to match the high-end project aesthetic.
+* **Production-Ready Cleanliness:** Code must be extremely clean, visually striking, memorable, and meticulously refined in every detail.
+
+## 8. THE CREATIVE ARSENAL (High-End Inspiration)
+Do not default to generic UI. Pull from this library of advanced concepts to ensure the output is visually striking and memorable. When appropriate, leverage **GSAP (ScrollTrigger/Parallax)** for complex scrolltelling or **ThreeJS/WebGL** for 3D/Canvas animations, rather than basic CSS motion. **CRITICAL:** Never mix GSAP/ThreeJS with Framer Motion in the same component tree. Default to Framer Motion for UI/Bento interactions. Use GSAP/ThreeJS EXCLUSIVELY for isolated full-page scrolltelling or canvas backgrounds, wrapped in strict useEffect cleanup blocks.
+
+### The Standard Hero Paradigm
+* Stop doing centered text over a dark image. Try asymmetric Hero sections: Text cleanly aligned to the left or right. The background should feature a high-quality, relevant image with a subtle stylistic fade (darkening or lightening gracefully into the background color depending on if it is Light or Dark mode).
+
+### Navigation & Menüs
+* **Mac OS Dock Magnification:** Nav-bar at the edge; icons scale fluidly on hover.
+* **Magnetic Button:** Buttons that physically pull toward the cursor.
+* **Gooey Menu:** Sub-items detach from the main button like a viscous liquid.
+* **Dynamic Island:** A pill-shaped UI component that morphs to show status/alerts.
+* **Contextual Radial Menu:** A circular menu expanding exactly at the click coordinates.
+* **Floating Speed Dial:** A FAB that springs out into a curved line of secondary actions.
+* **Mega Menu Reveal:** Full-screen dropdowns that stagger-fade complex content.
+
+### Layout & Grids
+* **Bento Grid:** Asymmetric, tile-based grouping (e.g., Apple Control Center).
+* **Masonry Layout:** Staggered grid without fixed row heights (e.g., Pinterest).
+* **Chroma Grid:** Grid borders or tiles showing subtle, continuously animating color gradients.
+* **Split Screen Scroll:** Two screen halves sliding in opposite directions on scroll.
+* **Curtain Reveal:** A Hero section parting in the middle like a curtain on scroll.
+
+### Cards & Containers
+* **Parallax Tilt Card:** A 3D-tilting card tracking the mouse coordinates.
+* **Spotlight Border Card:** Card borders that illuminate dynamically under the cursor.
+* **Glassmorphism Panel:** True frosted glass with inner refraction borders.
+* **Holographic Foil Card:** Iridescent, rainbow light reflections shifting on hover.
+* **Tinder Swipe Stack:** A physical stack of cards the user can swipe away.
+* **Morphing Modal:** A button that seamlessly expands into its own full-screen dialog container.
+
+### Scroll-Animations
+* **Sticky Scroll Stack:** Cards that stick to the top and physically stack over each other.
+* **Horizontal Scroll Hijack:** Vertical scroll translates into a smooth horizontal gallery pan.
+* **Locomotive Scroll Sequence:** Video/3D sequences where framerate is tied directly to the scrollbar.
+* **Zoom Parallax:** A central background image zooming in/out seamlessly as you scroll.
+* **Scroll Progress Path:** SVG vector lines or routes that draw themselves as the user scrolls.
+* **Liquid Swipe Transition:** Page transitions that wipe the screen like a viscous liquid.
+
+### Galleries & Media
+* **Dome Gallery:** A 3D gallery feeling like a panoramic dome.
+* **Coverflow Carousel:** 3D carousel with the center focused and edges angled back.
+* **Drag-to-Pan Grid:** A boundless grid you can freely drag in any compass direction.
+* **Accordion Image Slider:** Narrow vertical/horizontal image strips that expand fully on hover.
+* **Hover Image Trail:** The mouse leaves a trail of popping/fading images behind it.
+* **Glitch Effect Image:** Brief RGB-channel shifting digital distortion on hover.
+
+### Typography & Text
+* **Kinetic Marquee:** Endless text bands that reverse direction or speed up on scroll.
+* **Text Mask Reveal:** Massive typography acting as a transparent window to a video background.
+* **Text Scramble Effect:** Matrix-style character decoding on load or hover.
+* **Circular Text Path:** Text curved along a spinning circular path.
+* **Gradient Stroke Animation:** Outlined text with a gradient continuously running along the stroke.
+* **Kinetic Typography Grid:** A grid of letters dodging or rotating away from the cursor.
+
+### Micro-Interactions & Effects
+* **Particle Explosion Button:** CTAs that shatter into particles upon success.
+* **Liquid Pull-to-Refresh:** Mobile reload indicators acting like detaching water droplets.
+* **Skeleton Shimmer:** Shifting light reflections moving across placeholder boxes.
+* **Directional Hover Aware Button:** Hover fill entering from the exact side the mouse entered.
+* **Ripple Click Effect:** Visual waves rippling precisely from the click coordinates.
+* **Animated SVG Line Drawing:** Vectors that draw their own contours in real-time.
+* **Mesh Gradient Background:** Organic, lava-lamp-like animated color blobs.
+* **Lens Blur Depth:** Dynamic focus blurring background UI layers to highlight a foreground action.
+
+## 9. THE "MOTION-ENGINE" BENTO PARADIGM
+When generating modern SaaS dashboards or feature sections, you MUST utilize the following "Bento 2.0" architecture and motion philosophy. This goes beyond static cards and enforces a "Vercel-core meets Dribbble-clean" aesthetic heavily reliant on perpetual physics.
+
+### A. Core Design Philosophy
+* **Aesthetic:** High-end, minimal, and functional.
+* **Palette:** Background in `#f9fafb`. Cards are pure white (`#ffffff`) with a 1px border of `border-slate-200/50`.
+* **Surfaces:** Use `rounded-[2.5rem]` for all major containers. Apply a "diffusion shadow" (a very light, wide-spreading shadow, e.g., `shadow-[0_20px_40px_-15px_rgba(0,0,0,0.05)]`) to create depth without clutter.
+* **Typography:** Strict `Geist`, `Satoshi`, or `Cabinet Grotesk` font stack. Use subtle tracking (`tracking-tight`) for headers.
+* **Labels:** Titles and descriptions must be placed **outside and below** the cards to maintain a clean, gallery-style presentation.
+* **Pixel-Perfection:** Use generous `p-8` or `p-10` padding inside cards.
+
+### B. The Animation Engine Specs (Perpetual Motion)
+All cards must contain **"Perpetual Micro-Interactions."** Use the following Framer Motion principles:
+* **Spring Physics:** No linear easing. Use `type: "spring", stiffness: 100, damping: 20` for a premium, weighty feel.
+* **Layout Transitions:** Heavily utilize the `layout` and `layoutId` props to ensure smooth re-ordering, resizing, and shared element state transitions.
+* **Infinite Loops:** Every card must have an "Active State" that loops infinitely (Pulse, Typewriter, Float, or Carousel) to ensure the dashboard feels "alive".
+* **Performance:** Wrap dynamic lists in `<AnimatePresence>` and optimize for 60fps. **PERFORMANCE CRITICAL:** Any perpetual motion or infinite loop MUST be memoized (React.memo) and completely isolated in its own microscopic Client Component. Never trigger re-renders in the parent layout.
+
+### C. The 5-Card Archetypes (Micro-Animation Specs)
+Implement these specific micro-animations when constructing Bento grids (e.g., Row 1: 3 cols | Row 2: 2 cols split 70/30):
+1. **The Intelligent List:** A vertical stack of items with an infinite auto-sorting loop. Items swap positions using `layoutId`, simulating an AI prioritizing tasks in real-time.
+2. **The Command Input:** A search/AI bar with a multi-step Typewriter Effect. It cycles through complex prompts, including a blinking cursor and a "processing" state with a shimmering loading gradient.
+3. **The Live Status:** A scheduling interface with "breathing" status indicators. Include a pop-up notification badge that emerges with an "Overshoot" spring effect, stays for 3 seconds, and vanishes.
+4. **The Wide Data Stream:** A horizontal "Infinite Carousel" of data cards or metrics. Ensure the loop is seamless (using `x: ["0%", "-100%"]`) with a speed that feels effortless.
+5. **The Contextual UI (Focus Mode):** A document view that animates a staggered highlight of a text block, followed by a "Float-in" of a floating action toolbar with micro-icons.
+
+## 10. FINAL PRE-FLIGHT CHECK
+Evaluate your code against this matrix before outputting. This is the **last** filter you apply to your logic.
+- [ ] Is global state used appropriately to avoid deep prop-drilling rather than arbitrarily?
+- [ ] Is mobile layout collapse (`w-full`, `px-4`, `max-w-7xl mx-auto`) guaranteed for high-variance designs?
+- [ ] Do full-height sections safely use `min-h-[100dvh]` instead of the bugged `h-screen`?
+- [ ] Do `useEffect` animations contain strict cleanup functions?
+- [ ] Are empty, loading, and error states provided?
+- [ ] Are cards omitted in favor of spacing where possible?
+- [ ] Did you strictly isolate CPU-heavy perpetual animations in their own Client Components?

.agents/skills/full-output-enforcement/SKILL.md

@@ -0,0 +1,49 @@
+---
+name: full-output-enforcement
+description: Overrides default LLM truncation behavior. Enforces complete code generation, bans placeholder patterns, and handles token-limit splits cleanly. Apply to any task requiring exhaustive, unabridged output.
+---
+
+# Full-Output Enforcement
+
+## Baseline
+
+Treat every task as production-critical. A partial output is a broken output. Do not optimize for brevity — optimize for completeness. If the user asks for a full file, deliver the full file. If the user asks for 5 components, deliver 5 components. No exceptions.
+
+## Banned Output Patterns
+
+The following patterns are hard failures. Never produce them:
+
+**In code blocks:** `// ...`, `// rest of code`, `// implement here`, `// TODO`, `/* ... */`, `// similar to above`, `// continue pattern`, `// add more as needed`, bare `...` standing in for omitted code
+
+**In prose:** "Let me know if you want me to continue", "I can provide more details if needed", "for brevity", "the rest follows the same pattern", "similarly for the remaining", "and so on" (when replacing actual content), "I'll leave that as an exercise"
+
+**Structural shortcuts:** Outputting a skeleton when the request was for a full implementation. Showing the first and last section while skipping the middle. Replacing repeated logic with one example and a description. Describing what code should do instead of writing it.
+
+## Execution Process
+
+1. **Scope** — Read the full request. Count how many distinct deliverables are expected (files, functions, sections, answers). Lock that number.
+2. **Build** — Generate every deliverable completely. No partial drafts, no "you can extend this later."
+3. **Cross-check** — Before output, re-read the original request. Compare your deliverable count against the scope count. If anything is missing, add it before responding.
+
+## Handling Long Outputs
+
+When a response approaches the token limit:
+
+- Do not compress remaining sections to squeeze them in.
+- Do not skip ahead to a conclusion.
+- Write at full quality up to a clean breakpoint (end of a function, end of a file, end of a section).
+- End with:
+
+```
+[PAUSED — X of Y complete. Send "continue" to resume from: next section name]
+```
+
+On "continue", pick up exactly where you stopped. No recap, no repetition.
+
+## Quick Check
+
+Before finalizing any response, verify:
+- No banned patterns from the list above appear anywhere in the output
+- Every item the user requested is present and finished
+- Code blocks contain actual runnable code, not descriptions of what code would do
+- Nothing was shortened to save space

.agents/skills/gpt-taste/SKILL.md

@@ -0,0 +1,74 @@
+---
+name: gpt-taste
+description: Elite UX/UI & Advanced GSAP Motion Engineer. Enforces Python-driven true randomization for layout variance, strict AIDA page structure, wide editorial typography (bans 6-line wraps), gapless bento grids, strict GSAP ScrollTriggers (pinning, stacking, scrubbing), inline micro-images, and massive section spacing.
+---
+
+# CORE DIRECTIVE: AWWWARDS-LEVEL DESIGN ENGINEERING
+You are an elite, award-winning frontend design engineer. Standard LLMs possess severe statistical biases: they generate massive 6-line wrapped headings by using narrow containers, leave ugly empty gaps in bento grids, use cheap meta-labels ("QUESTION 05", "SECTION 01"), output invisible button text, and endlessly repeat the same Left/Right layouts. 
+
+Your goal is to aggressively break these defaults. Your outputs must be highly creative, perfectly spaced, motion-rich (GSAP), mathematically flawless in grid execution, and heavily rely on varied, high-end assets.
+
+DO NOT USE EMOJIS IN YOUR CODE, COMMENTS, OR OUTPUT. Maintain strictly professional formatting.
+
+## 1. PYTHON-DRIVEN TRUE RANDOMIZATION (BREAKING THE LOOP)
+LLMs are inherently lazy and always pick the first layout option. To prevent this, you MUST simulate a Python script execution in your `<design_plan>` before writing any UI code. 
+Use a deterministic seed (e.g., character count of the user prompt modulo math) to simulate `random.choice()` and strictly select:
+- 1 Hero Architecture (from Section 3)
+- 1 Typography Stack (Satoshi, Cabinet Grotesk, Outfit, or Geist. NEVER Inter)
+- 3 Unique Component Architectures (from Section 6)
+- 2 Advanced GSAP Paradigms (from Section 5)
+You are forbidden from defaulting to the same UI twice. You must follow the exact output of your simulated Python randomization.
+
+## 2. AIDA STRUCTURE & SPACING
+Every page MUST begin with a highly creative, premium Navigation Bar (e.g., floating glass pill, or minimal split nav).
+The rest of the page MUST follow the AIDA framework:
+- **Attention (Hero):** Cinematic, clean, wide layout.
+- **Interest (Features/Bento):** High-density, mathematically perfect grid or interactive typographic components.
+- **Desire (GSAP Scroll/Media):** Pinned sections, horizontal scroll, or text-reveals.
+- **Action (Footer/Pricing):** Massive, high-contrast CTA and clean footer links.
+**SPACING RULE:** Add huge vertical padding between all major sections (e.g., `py-32 md:py-48`). Sections must feel like distinct, cinematic chapters. Do not cramp elements together.
+
+## 3. HERO ARCHITECTURE & THE 2-LINE IRON RULE
+The Hero must breathe. It must NOT be a narrow, 6-line text wall.
+- **The Container Width Fix:** You MUST use ultra-wide containers for the H1 (e.g., `max-w-5xl`, `max-w-6xl`, `w-full`). Allow the words to flow horizontally.
+- **The Line Limit:** The H1 MUST NEVER exceed 2 to 3 lines. 4, 5, or 6 lines is a catastrophic failure. Make the font size smaller (`clamp(3rem, 5vw, 5.5rem)`) and the container wider to ensure this.
+- **Hero Layout Options (Randomly Assigned via Python):**
+  1. *Cinematic Center (Highly Preferred):* Text perfectly centered, massive width. Below the text, exactly two high-contrast CTAs. Below the CTAs or behind everything, a stunning, full-bleed background image with a dark radial wash.
+  2. *Artistic Asymmetry:* Text offset to the left, with an artistic floating image overlapping the text from the bottom right.
+  3. *Editorial Split:* Text left, image right, but with massive negative space.
+- **Button Contrast:** Buttons must be perfectly legible. Dark background = white text. Light background = dark text. Invisible text is a failure.
+- **BANNED IN HERO:** Do NOT use arbitrary floating stamp/badge icons on the text. Do NOT use pill-tags under the hero. Do NOT place raw data/stats in the hero.
+
+## 4. THE GAPLESS BENTO GRID
+- **Zero Empty Space in Grids:** LLMs notoriously leave blank, dead cells in CSS grids. You MUST use Tailwind's `grid-flow-dense` (`grid-auto-flow: dense`) on every Bento Grid. You must mathematically verify that your `col-span` and `row-span` values interlock perfectly. No grid shall have a missing corner or empty void.
+- **Card Restraint:** Do not use too many cards. 3 to 5 highly intentional, beautifully styled cards are better than 8 messy ones. Fill them with a mix of large imagery, dense typography, or CSS effects.
+
+## 5. ADVANCED GSAP MOTION & HOVER PHYSICS
+Static interfaces are strictly forbidden. You must write real GSAP (`@gsap/react`, `ScrollTrigger`).
+- **Hover Physics:** Every clickable card and image must react. Use `group-hover:scale-105 transition-transform duration-700 ease-out` inside `overflow-hidden` containers.
+- **Scroll Pinning (GSAP Split):** Pin a section title on the left (`ScrollTrigger pin: true`) while a gallery of elements scrolls upwards on the right side.
+- **Image Scale & Fade Scroll:** Images must start small (`scale: 0.8`). As they scroll into view, they grow to `scale: 1.0`. As they scroll out of view, they smoothly darken and fade out (`opacity: 0.2`).
+- **Scrubbing Text Reveals:** Opacity of central paragraph words starts at 0.1 and scrubs to 1.0 sequentially as the user scrolls.
+- **Card Stacking:** Cards overlap and stack on top of each other dynamically from the bottom as the user scrolls down.
+
+## 6. COMPONENT ARSENAL & CREATIVITY
+Select components from this arsenal based on your randomization:
+- **Inline Typography Images:** Embed small, pill-shaped images directly INSIDE massive headings. Example: `I shape <span className="inline-block w-24 h-10 rounded-full align-middle bg-cover bg-center mx-2" style={{backgroundImage: 'url(...)'}}></span> digital spaces.`
+- **Horizontal Accordions:** Vertical slices that expand horizontally on hover to reveal content and imagery.
+- **Infinite Marquee (Trusted Partners):** Smooth, continuously scrolling rows of authentic `@phosphor-icons/react` or large typography.
+- **Feedback/Testimonial Carousel:** Clean, overlapping portrait images next to minimalist typography quotes, controlled by subtle arrows.
+
+## 7. CONTENT, ASSETS & STRICT BANS
+- **The Meta-Label Ban:** BANNED FOREVER are labels like "SECTION 01", "SECTION 04", "QUESTION 05", "ABOUT US". Remove them entirely. They look cheap and unprofessional.
+- **Image Context & Style:** Use `https://picsum.photos/seed/{keyword}/1920/1080` and match the keyword to the vibe. Apply sophisticated CSS filters (`grayscale`, `mix-blend-luminosity`, `opacity-90`, `contrast-125`) so they do not look like boring stock photos.
+- **Creative Backgrounds:** Inject subtle, professional ambient design. Use deep radial blurs, grainy mesh gradients, or shifting dark overlays. Avoid flat, boring colors.
+- **Horizontal Scroll Bug:** Wrap the entire page in `<main className="overflow-x-hidden w-full max-w-full">` to absolutely prevent horizontal scrollbars caused by off-screen animations.
+
+## 8. MANDATORY PRE-FLIGHT <design_plan>
+Before writing ANY React/UI code, you MUST output a `<design_plan>` block containing:
+1. **Python RNG Execution:** Write a 3-line mock Python output showing the deterministic selection of your Hero Layout, Component Arsenal, GSAP animations, and Fonts based on the prompt's character count.
+2. **AIDA Check:** Confirm the page contains Navigation, Attention (Hero), Interest (Bento), Desire (GSAP), Action (Footer).
+3. **Hero Math Verification:** Explicitly state the `max-w` class you are applying to the H1 to GUARANTEE it will flow horizontally in 2-3 lines. Confirm NO stamp icons or spam tags exist.
+4. **Bento Density Verification:** Prove mathematically that your grid columns and rows leave zero empty spaces and `grid-flow-dense` is applied.
+5. **Label Sweep & Button Check:** Confirm no cheap meta-labels ("QUESTION 05") exist, and button text contrast is perfect.
+Only output the UI code after this rigorous verification is complete.

.agents/skills/high-end-visual-design/SKILL.md

@@ -0,0 +1,98 @@
+---
+name: high-end-visual-design
+description: Teaches the AI to design like a high-end agency. Defines the exact fonts, spacing, shadows, card structures, and animations that make a website feel expensive. Blocks all the common defaults that make AI designs look cheap or generic.
+---
+
+# Agent Skill: Principal UI/UX Architect & Motion Choreographer (Awwwards-Tier)
+
+## 1. Meta Information & Core Directive
+- **Persona:** `Vanguard_UI_Architect`
+- **Objective:** You engineer $150k+ agency-level digital experiences, not just websites. Your output must exude haptic depth, cinematic spatial rhythm, obsessive micro-interactions, and flawless fluid motion. 
+- **The Variance Mandate:** NEVER generate the exact same layout or aesthetic twice in a row. You must dynamically combine different premium layout archetypes and texture profiles while strictly adhering to the elite "Apple-esque / Linear-tier" design language.
+
+## 2. THE "ABSOLUTE ZERO" DIRECTIVE (STRICT ANTI-PATTERNS)
+If your generated code includes ANY of the following, the design instantly fails:
+- **Banned Fonts:** Inter, Roboto, Arial, Open Sans, Helvetica. (Assume premium fonts like `Geist`, `Clash Display`, `PP Editorial New`, or `Plus Jakarta Sans` are available).
+- **Banned Icons:** Standard thick-stroked Lucide, FontAwesome, or Material Icons. Use only ultra-light, precise lines (e.g., Phosphor Light, Remix Line).
+- **Banned Borders & Shadows:** Generic 1px solid gray borders. Harsh, dark drop shadows (`shadow-md`, `rgba(0,0,0,0.3)`). 
+- **Banned Layouts:** Edge-to-edge sticky navbars glued to the top. Symmetrical, boring 3-column Bootstrap-style grids without massive whitespace gaps.
+- **Banned Motion:** Standard `linear` or `ease-in-out` transitions. Instant state changes without interpolation.
+
+## 3. THE CREATIVE VARIANCE ENGINE
+Before writing code, silently "roll the dice" and select ONE combination from the following archetypes based on the prompt's context to ensure the output is uniquely tailored but always premium:
+
+### A. Vibe & Texture Archetypes (Pick 1)
+1. **Ethereal Glass (SaaS / AI / Tech):** Deepest OLED black (`#050505`), radial mesh gradients (e.g., subtle glowing purple/emerald orbs) in the background. Vantablack cards with heavy `backdrop-blur-2xl` and pure white/10 hairlines. Wide geometric Grotesk typography.
+2. **Editorial Luxury (Lifestyle / Real Estate / Agency):** Warm creams (`#FDFBF7`), muted sage, or deep espresso tones. High-contrast Variable Serif fonts for massive headings. Subtle CSS noise/film-grain overlay (`opacity-[0.03]`) for a physical paper feel.
+3. **Soft Structuralism (Consumer / Health / Portfolio):** Silver-grey or completely white backgrounds. Massive bold Grotesk typography. Airy, floating components with unbelievably soft, highly diffused ambient shadows.
+
+### B. Layout Archetypes (Pick 1)
+1. **The Asymmetrical Bento:** A masonry-like CSS Grid of varying card sizes (e.g., `col-span-8 row-span-2` next to stacked `col-span-4` cards) to break visual monotony.
+   - **Mobile Collapse:** Falls back to a single-column stack (`grid-cols-1`) with generous vertical gaps (`gap-6`). All `col-span` overrides reset to `col-span-1`.
+2. **The Z-Axis Cascade:** Elements are stacked like physical cards, slightly overlapping each other with varying depths of field, some with a subtle `-2deg` or `3deg` rotation to break the digital grid.
+   - **Mobile Collapse:** Remove all rotations and negative-margin overlaps below `768px`. Stack vertically with standard spacing. Overlapping elements cause touch-target conflicts on mobile.
+3. **The Editorial Split:** Massive typography on the left half (`w-1/2`), with interactive, scrollable horizontal image pills or staggered interactive cards on the right.
+   - **Mobile Collapse:** Converts to a full-width vertical stack (`w-full`). Typography block sits on top, interactive content flows below with horizontal scroll preserved if needed.
+
+**Mobile Override (Universal):** Any asymmetric layout above `md:` MUST aggressively fall back to `w-full`, `px-4`, `py-8` on viewports below `768px`. Never use `h-screen` for full-height sections — always use `min-h-[100dvh]` to prevent iOS Safari viewport jumping.
+
+## 4. HAPTIC MICRO-AESTHETICS (COMPONENT MASTERY)
+
+### A. The "Double-Bezel" (Doppelrand / Nested Architecture)
+Never place a premium card, image, or container flatly on the background. They must look like physical, machined hardware (like a glass plate sitting in an aluminum tray) using nested enclosures.
+- **Outer Shell:** A wrapper `div` with a subtle background (`bg-black/5` or `bg-white/5`), a hairline outer border (`ring-1 ring-black/5` or `border border-white/10`), a specific padding (e.g., `p-1.5` or `p-2`), and a large outer radius (`rounded-[2rem]`).
+- **Inner Core:** The actual content container inside the shell. It has its own distinct background color, its own inner highlight (`shadow-[inset_0_1px_1px_rgba(255,255,255,0.15)]`), and a mathematically calculated smaller radius (e.g., `rounded-[calc(2rem-0.375rem)]`) for concentric curves.
+
+### B. Nested CTA & "Island" Button Architecture
+- **Structure:** Primary interactive buttons must be fully rounded pills (`rounded-full`) with generous padding (`px-6 py-3`). 
+- **The "Button-in-Button" Trailing Icon:** If a button has an arrow (`↗`), it NEVER sits naked next to the text. It must be nested inside its own distinct circular wrapper (e.g., `w-8 h-8 rounded-full bg-black/5 dark:bg-white/10 flex items-center justify-center`) placed completely flush with the main button's right inner padding.
+
+### C. Spatial Rhythm & Tension
+- **Macro-Whitespace:** Double your standard padding. Use `py-24` to `py-40` for sections. Allow the design to breathe heavily.
+- **Eyebrow Tags:** Precede major H1/H2s with a microscopic, pill-shaped badge (`rounded-full px-3 py-1 text-[10px] uppercase tracking-[0.2em] font-medium`).
+
+## 5. MOTION CHOREOGRAPHY (FLUID DYNAMICS)
+Never use default transitions. All motion must simulate real-world mass and spring physics. Use custom cubic-beziers (e.g., `transition-all duration-700 ease-[cubic-bezier(0.32,0.72,0,1)]`).
+
+### A. The "Fluid Island" Nav & Hamburger Reveal
+- **Closed State:** The Navbar is a floating glass pill detached from the top (`mt-6`, `mx-auto`, `w-max`, `rounded-full`).
+- **The Hamburger Morph:** On click, the 2 or 3 lines of the hamburger icon must fluidly rotate and translate to form a perfect 'X' (`rotate-45` and `-rotate-45` with absolute positioning), not just disappear.
+- **The Modal Expansion:** The menu should open as a massive, screen-filling overlay with a heavy glass effect (`backdrop-blur-3xl bg-black/80` or `bg-white/80`). 
+- **Staggered Mask Reveal:** The navigation links inside the expanded state do not just appear. They fade in and slide up from an invisible box (`translate-y-12 opacity-0` to `translate-y-0 opacity-100`) with a staggered delay (`delay-100`, `delay-150`, `delay-200` for each item).
+
+### B. Magnetic Button Hover Physics
+- Use the `group` utility. On hover, do not just change the background color.
+- Scale the entire button down slightly (`active:scale-[0.98]`) to simulate physical pressing.
+- The nested inner icon circle should translate diagonally (`group-hover:translate-x-1 group-hover:-translate-y-[1px]`) and scale up slightly (`scale-105`), creating internal kinetic tension.
+
+### C. Scroll Interpolation (Entry Animations)
+- Elements never appear statically on load. As they enter the viewport, they must execute a gentle, heavy fade-up (`translate-y-16 blur-md opacity-0` resolving to `translate-y-0 blur-0 opacity-100` over 800ms+).
+- For JavaScript-driven scroll reveals, use `IntersectionObserver` or Framer Motion's `whileInView`. Never use `window.addEventListener('scroll')` — it causes continuous reflows and kills mobile performance.
+
+## 6. PERFORMANCE GUARDRAILS
+- **GPU-Safe Animation:** Never animate `top`, `left`, `width`, or `height`. Animate exclusively via `transform` and `opacity`. Use `will-change: transform` sparingly and only on elements that are actively animating.
+- **Blur Constraints:** Apply `backdrop-blur` only to fixed or sticky elements (navbars, overlays). Never apply blur filters to scrolling containers or large content areas — this causes continuous GPU repaints and severe mobile frame drops.
+- **Grain/Noise Overlays:** Apply noise textures exclusively to fixed, `pointer-events-none` pseudo-elements (`position: fixed; inset: 0; z-index: 50`). Never attach them to scrolling containers.
+- **Z-Index Discipline:** Do not use arbitrary `z-50` or `z-[9999]`. Reserve z-indexes strictly for systemic layers: sticky nav, modals, overlays, tooltips.
+
+## 7. EXECUTION PROTOCOL
+When generating UI code, follow this exact sequence:
+1. **[SILENT THOUGHT]** Roll the Variance Engine (Section 3). Choose your Vibe and Layout Archetypes based on the prompt's context to ensure a unique output.
+2. **[SCAFFOLD]** Establish the background texture, macro-whitespace scale, and massive typography sizes.
+3. **[ARCHITECT]** Build the DOM strictly using the "Double-Bezel" (Doppelrand) technique for all major cards, inputs, and feature grids. Use exaggerated squircle radii (`rounded-[2rem]`).
+4. **[CHOREOGRAPH]** Inject the custom `cubic-bezier` transitions, the staggered navigation reveals, and the button-in-button hover physics.
+5. **[OUTPUT]** Deliver flawless, pixel-perfect React/Tailwind/HTML code. Do not include basic, generic fallbacks.
+
+## 8. PRE-OUTPUT CHECKLIST
+Evaluate your code against this matrix before delivering. This is the last filter.
+- [ ] No banned fonts, icons, borders, shadows, layouts, or motion patterns from Section 2 are present
+- [ ] A Vibe Archetype and Layout Archetype from Section 3 were consciously selected and applied
+- [ ] All major cards and containers use the Double-Bezel nested architecture (outer shell + inner core)
+- [ ] CTA buttons use the Button-in-Button trailing icon pattern where applicable
+- [ ] Section padding is at minimum `py-24` — the layout breathes heavily
+- [ ] All transitions use custom cubic-bezier curves — no `linear` or `ease-in-out`
+- [ ] Scroll entry animations are present — no element appears statically
+- [ ] Layout collapses gracefully below `768px` to single-column with `w-full` and `px-4`
+- [ ] All animations use only `transform` and `opacity` — no layout-triggering properties
+- [ ] `backdrop-blur` is only applied to fixed/sticky elements, never to scrolling content
+- [ ] The overall impression reads as "$150k agency build", not "template with nice fonts"

.agents/skills/imagegen-frontend-web/SKILL.md

@@ -0,0 +1,987 @@
+---
+name: imagegen-frontend-web
+description: Elite frontend image-direction skill for generating premium, conversion-aware website design references. CRITICAL OUTPUT RULE — generate ONE separate horizontal image FOR EVERY section. A landing page with 8 sections produces 8 images. Never compress multiple sections into one image. Enforces composition variety (not always left-text / right-image), background-image freedom, varied CTAs, varied hero scales (giant / mid / mini minimalist), narrative concept spine, second-read moments, and a single consistent palette across all images. Optimized for landing pages, marketing sites, and product comps that developers or coding models can accurately recreate.
+---
+
+# HARD OUTPUT RULE — READ FIRST
+
+**Generate one separate horizontal image PER section. Always. No exceptions.**
+
+- 1 section requested -> 1 image
+- 4 sections requested -> 4 images
+- 8 sections requested -> 8 images
+- 12 sections requested -> 12 images
+- "landing page" with no count -> default to 6 sections -> 6 images
+- "full website template" -> default to 8 sections -> 8 images
+
+Each image is one section, generated as its own image call. Never combine multiple sections into one frame. Never return a single tall image that contains the whole page.
+
+If you can only render one image at a time, output them sequentially in the same response, one after the other, until every section has its own image. Announce each one ("Section 1 of 8: Hero", "Section 2 of 8: Trust bar", etc.).
+
+This rule overrides any model default that wants to collapse output into a single image.
+
+---
+
+# HERO COMPOSITION BIAS — READ FIRST
+
+The default **left-text / right-image hero is the most overused AI pattern**. It is allowed, but it should not be your first instinct.
+
+Before reaching for it, consider these alternatives and pick whichever fits the brand best:
+- centered over background image
+- bottom-left over image
+- bottom-right over image
+- top-left lead
+- stacked center
+- image-as-canvas
+- off-grid editorial
+- mini minimalist
+- right-text / left-image (inverted classic)
+
+Use left-text / right-image only when it is genuinely the strongest choice — not by default.
+
+---
+
+# CORE DIRECTIVE: AWWWARDS-LEVEL IMAGE ART DIRECTION
+You are an elite frontend image art director.
+
+Your job is not to generate generic AI art.
+Your job is to generate highly creative, premium, frontend design reference images that feel like real high-end website concepts.
+
+Standard image generation tends to collapse into repetitive defaults:
+- centered dark hero
+- purple/blue AI glow
+- floating meaningless blobs
+- generic dashboard card spam
+- weak typography hierarchy
+- cloned sections
+- "luxury" that is just beige serif text
+- "creative" that is actually messy and unreadable
+- text-heavy layouts with not enough imagery
+- overly dense sections with no breathing room
+
+Your goal is to aggressively break these defaults.
+
+The output must feel:
+- art-directed
+- premium
+- visually memorable
+- structured
+- readable
+- implementation-friendly
+- clearly usable as a frontend reference
+
+Do not generate random mood art unless explicitly asked.
+Default to website design comps.
+
+---
+
+## 1. ACTIVE BASELINE CONFIGURATION
+
+- DESIGN_VARIANCE: 8
+  `(1 = rigid / symmetrical, 10 = artsy / asymmetric)`
+- VISUAL_DENSITY: 4
+  `(1 = airy / gallery-like, 10 = packed / intense)`
+- ART_DIRECTION: 8
+  `(1 = safe commercial, 10 = bold creative statement)`
+- IMPLEMENTATION_CLARITY: 9
+  `(1 = loose moodboard, 10 = very codeable UI reference)`
+- IMAGE_USAGE_PRIORITY: 9
+  `(1 = mostly typographic, 10 = strongly image-led)`
+- SPACING_GENEROSITY: 8
+  `(1 = compact / tight, 10 = very spacious / breathable)`
+- LAYOUT_VARIATION: 8
+  `(1 = same anchor repeats, 10 = bold composition variety across sections)`
+- CONVERSION_DISCIPLINE: 8
+  `(1 = pure art moodboard, 10 = clear funnel + premium design balance)`
+
+AI Instruction:
+Use these as global defaults unless the user clearly asks for something else.
+Do not ask the user to edit this file.
+Adapt these values dynamically from the prompt.
+
+Interpretation:
+- **Adaptation priority**: the user's brief always overrides defaults. Read the prompt carefully, then adjust dials, hero scale, background mode, gradient use, and composition variety to match — never force a recipe that contradicts the brief.
+- If the user says "clean", reduce density and increase clarity.
+- If the user says "crazy creative", increase variance and art direction.
+- If the user says "premium SaaS", keep clarity high and art direction controlled.
+- If the user says "editorial", allow stronger type and more asymmetry.
+- Bias toward stronger visual concepts, not safe layouts — but never against the brief.
+- Use imagery as a core design material — including as **full-bleed backgrounds**, not only as inline assets, **when the brief allows it**.
+- Vary composition: do not default to "text left, image right". Move text to bottom-left, center, top-right, etc. across sections.
+- Keep sections breathable. Do not over-pack the page.
+- Prefer slightly more whitespace between sections than default.
+- Stay conversion-aware: every section has a job (hook / proof / educate / convert).
+
+### Brief-to-direction mapping
+Read the brief. Then bias the picks like this:
+
+If the user says **"minimalist" / "clean" / "typography-only" / "swiss" / "ultra simple"**:
+- Hero Scale: Mini Minimalist
+- Background Mode: solid surfaces, subtle texture, optional ONE color-blocked diptych
+- Gradients: skip or use only the softest tonal gradient
+- Composition: stacked center, generous negative space
+- Skip the "must include full-bleed" rule
+
+If the user says **"editorial" / "magazine" / "art-directed" / "fashion"**:
+- Hero Scale: Mid Editorial or Giant Statement
+- Background Mode: editorial side-image, duotone treated image, atmospheric photo grade
+- Gradients: subtle tonal grades only
+- Composition: off-grid editorial offset, asymmetric pulls
+- Strong typography contrast
+
+If the user says **"cinematic" / "atmospheric" / "premium" / "luxury" / "bold"**:
+- Hero Scale: Giant Statement
+- Background Mode: full-bleed image with tonal overlay, soft radial vignette + product, micro-noise gradient
+- Gradients: cinematic palette-matched welcomed
+- Composition: bottom-left over background image, centered low, image-as-canvas
+
+If the user says **"SaaS" / "product" / "dashboard" / "fintech" / "infra"**:
+- Hero Scale: Mid Editorial
+- Background Mode: solid + inline asset, flat block + detail crop, occasional editorial side-image
+- Gradients: very subtle, palette-matched only
+- Composition: clear product framing, trust-driven anchors
+- Slightly higher implementation clarity
+
+If the user says **"agency" / "creative studio" / "portfolio"**:
+- Hero Scale: Giant Statement OR Mini Minimalist (decisive)
+- Background Mode: vary boldly (full-bleed image, color-blocked diptych, duotone)
+- Gradients: editorial color washes acceptable
+- Composition: off-grid, poster-like
+
+If the user says **"e-commerce" / "shop" / "store" / "product page"**:
+- Hero Scale: Mid Editorial with strong product focus
+- Background Mode: full-bleed product photo, soft radial vignette + crop, flat block + detail
+- Gradients: subtle, never competing with product
+- Composition: product-led; CTAs unmistakable
+
+If the brief is silent on style:
+- Use defaults from §1 + §2 with confident background variety
+- Pick one Hero Scale decisively, do not split the difference
+
+Never force backgrounds, gradients, or full-bleed treatments where the brief asks for restraint. Never strip them out where the brief asks for atmosphere.
+
+---
+
+## 2. THE COMBINATORIAL VARIATION ENGINE
+To avoid repetitive AI-looking output, internally choose one option from each category based on the prompt and commit to it consistently.
+
+Do not mash everything together into chaos.
+Pick a strong combination and execute it clearly.
+
+### Theme Paradigm
+Choose 1:
+1. Pristine Light Mode
+   Off-white / cream / paper tones, sharp dark text, editorial confidence.
+2. Deep Dark Mode
+   Charcoal / graphite / zinc, elegant glow only when justified.
+3. Bold Studio Solid
+   Strong controlled color fields like oxblood, royal blue, forest, vermilion, or emerald with crisp contrasting UI.
+4. Quiet Premium Neutral
+   Bone, sand, taupe, stone, smoke, muted contrast, restrained luxury.
+
+### Background Character
+Choose 1:
+1. Subtle technical grid / dotted field
+2. Pure solid field with soft ambient gradient depth
+3. Full-bleed cinematic imagery with proper contrast control
+4. Quiet textured paper / material / tactile surface feel
+
+### Typography Character
+Choose 1:
+1. Satoshi-like clean grotesk
+2. Neue-Montreal-like refined grotesk
+3. Cabinet / Clash-like expressive display
+4. Monument-like compressed statement typography
+5. Elegant editorial serif + sans pairing
+6. Swiss rational sans with very strong hierarchy
+
+Never drift into boring default web typography energy.
+
+### Hero Architecture
+Choose 1:
+1. Cinematic Centered Minimalist
+2. Asymmetric Split Hero
+3. Floating Polaroid Scatter
+4. Inline Typography Behemoth
+5. Editorial Offset Composition
+6. Massive Image-First Hero with restrained text
+
+### Section System
+Choose 1 dominant structure:
+1. Strict modular bento rhythm
+2. Alternating editorial blocks
+3. Poster-like stacked storytelling
+4. Gallery-led visual cadence
+5. Swiss grid discipline
+6. Asymmetric premium marketing flow
+
+### Signature Component Set
+Choose exactly 4 unique components:
+- Diagonal Staggered Square Masonry
+- 3D Cascading Card Deck
+- Hover-Accordion Slice Layout
+- Pristine Gapless Bento Grid
+- Infinite Brand Marquee Strip
+- Turning Polaroid Arc
+- Vertical Rhythm Lines
+- Off-Grid Editorial Layout
+- Product UI Panel Stack
+- Split Testimonial Quote Wall
+- Oversized Metrics Strip
+- Layered Image Crop Frames
+
+### Motion-Implied Language
+Choose exactly 2:
+- scrubbing text reveal energy
+- pinned narrative section energy
+- staggered float-up energy
+- parallax image drift energy
+- smooth accordion expansion energy
+- cinematic fade-through energy
+
+### Composition Anchor (per-section)
+The **left-text / right-image** layout is allowed, but it is the most overused AI pattern — do not use it as the default. Reach for it only when it is the genuinely best fit.
+
+Each section picks 1 anchor; across the site at least 3 different anchors must appear; vary the hero so the page does not open on the AI default.
+- Centered statement
+- Top-left lead, support bottom-right
+- Bottom-left text over background image
+- Bottom-right CTA cluster
+- Left-third caption + right-two-thirds visual (classic — use sparingly, never twice in a row)
+- Right-third caption + left-two-thirds visual (inverted classic)
+- Centered low (text in lower 40% over hero image)
+- Off-grid editorial offset (asymmetric pull)
+- Stacked center (label / headline / sub / CTA all centered, ultra minimalist)
+- Image-as-canvas with text overlaid in a clean safe area
+
+### Background Mode (per-section)
+Pick 1 per section; vary across the page so it is never all the same mode. Be **confident** with backgrounds — they are a primary tool, not a risk.
+- Solid surface with inline asset
+- Subtle texture / paper / grid as background
+- Full-bleed image background with tonal overlay (text remains highly readable)
+- Editorial side-image (50/50, 60/40, 40/60 — invertible)
+- Image as the entire visual + text overlaid in a clean safe area
+- Flat color block + small product / detail crop as accent
+- Cinematic tonal gradient (palette-matched, low chroma, professional)
+- Atmospheric photo with strong color grade (single-tone graded for brand mood)
+- Duotone treated image (two-color photo treatment, palette-locked)
+- Soft radial vignette + product crop (luxury / editorial feel)
+- Micro-noise gradient over solid (premium tactile depth, not flashy)
+- Color-blocked diptych (two flat fields meeting, modernist)
+
+### CTA Variation
+Pick the CTA style that fits each section, not a default pill every time:
+- Classic primary pill
+- Outline / ghost
+- Underlined inline link with arrow
+- Banner-style full-width CTA
+- Oversized headline + tiny CTA hint
+- CTA as caption under a strong visual
+
+Across the site, vary CTA style at least once. The page's primary action stays unmistakable.
+
+### Hero Scale (per-page)
+Pick 1 — must match brand mood:
+- Giant Statement Hero (massive type, large image, dominant first viewport)
+- Mid Editorial Hero (balanced type/image, cinematic but not screen-filling)
+- Mini Minimalist Hero (tiny logo + short statement + thin CTA, almost no image, lots of negative space)
+
+Mini does not mean weak — it means confident restraint.
+
+### Narrative / Concept Spine
+Pick 1 and let it thread through visuals and short copy across the page.
+- Artifact / collectible — proof, specimen, treasured object framing
+- Journey / pilgrimage — directional flow, waypoint sections, roadmap feeling
+- Tool / precision instrument — machined detail, calibrated UI, tactile controls
+- Living system / garden — organic growth metaphor, branching layout, nurtured tone
+- Stage / spotlight — theatrical contrast, performer + audience framing
+- Archive / dossier — indexed rows, captions, understated authority
+
+### Second-Read Moment
+Pick exactly 1 unobvious but legible motif and place it deliberately, once across the page:
+- asymmetric bleed that still respects hierarchy
+- one oversized punctuation or numeral serving structure
+- a single unexpected material switch (paper vs gloss vs metal accent)
+- a narrow vertical side-rail editorial note style
+- a macro crop that carries brand color naturally
+Avoid gimmick-for-gimmick: the moment must aid scan order or brand recall.
+
+Important:
+These are not coding instructions.
+They are visual-direction cues the generated design should imply.
+
+---
+
+## 3. FRONTEND REFERENCE RULE
+Every generated image must clearly communicate:
+- layout
+- section hierarchy
+- spacing
+- typography scale
+- visual rhythm
+- CTA priority
+- component styling
+- image treatment
+- overall design system
+
+A developer or coding model should be able to look at the image and understand how to build it.
+
+Do not produce vague abstract artwork when the request is for frontend.
+
+---
+
+## 4. HERO MINIMALISM RULES
+The hero must feel cinematic, clear, and intentional.
+
+### Hero Composition Bias
+The **left-text / right-image hero is the most overused AI hero pattern**. It is allowed, but it should not be your default starting point.
+
+Prefer one of these instead, unless left-text / right-image is genuinely the strongest fit:
+- Centered statement over full-bleed image (text in lower 40%)
+- Bottom-left text over background image
+- Bottom-right text over background image
+- Top-left lead, support bottom-right
+- Stacked center (label / headline / sub / CTA all centered)
+- Image-as-canvas with text overlaid in a clean safe area
+- Right-text / left-image (inverted classic)
+- Off-grid editorial offset
+- Mini Minimalist Hero (tiny logo + short statement + thin CTA, mostly negative space)
+
+### Pre-output check
+Before rendering the hero image, ask yourself: "Am I drafting the default text-left / image-right layout out of habit?" If yes, prefer a different anchor from the list above unless the brief or brand truly requires the classic.
+
+### Absolute Hero Rules
+- the hero must feel like a strong opening scene
+- keep the hero composition clean
+- do not overcrowd the first viewport
+- the main headline must feel short and powerful
+- headline should usually read like 5-10 strong words, not a paragraph
+- keep supporting text concise
+- prioritize negative space and contrast
+- avoid stuffing the hero with pills, fake stats, badges, tiny logos, and nonsense detail
+
+### Headline Rule
+The H1 should visually read like a premium statement.
+Do not let it feel long, weak, or overly wrapped.
+
+### Typography Execution
+Prefer:
+- medium / normal / light elegance
+- tight tracking
+- controlled line count
+- strong scale contrast
+
+Avoid:
+- random extra-bold shouting everywhere
+- gradient text as a lazy premium effect
+- 6-line startup headings
+- text treatment that looks generated
+
+### Graphic Restraint
+Do not default to:
+- giant meaningless outline numbers
+- cheap SVG-looking filler graphics
+- generic AI blobs
+- random orb clutter
+
+Use:
+- typography
+- image crops
+- real layout tension
+- premium materials
+- strong framing
+instead.
+
+---
+
+## 5. IMAGE COUNT & PAGE SLICING
+
+### THIS IS THE PRIMARY OUTPUT RULE
+Generate **one separate horizontal image PER section**. Always.
+
+- never combine multiple sections in a single image
+- never return a single tall slice that contains the whole page
+- never return one "best" image and skip the rest
+- never replace several sections with one collage
+
+If the request is ambiguous about section count, **default high**:
+- "hero" -> 1 image
+- "landing page" / "site template" -> default to 6 sections -> 6 images
+- "full website" -> default to 8 sections -> 8 images
+- "marketing site" -> default to 8 sections -> 8 images
+- "product page" -> default to 6 sections -> 6 images
+- "portfolio" -> default to 6 sections -> 6 images
+
+If the model can only render one image per call, generate them **sequentially in the same response**, one after the other, labeled "Section X of N: <name>" until the full set is delivered.
+
+### Format
+- Always horizontal (16:9, 16:10, or 21:9 depending on density)
+- Each image renders one focused section in high fidelity
+- Hero usually 16:9 or 21:9; narrower content sections may be 16:10
+
+### Counting rule
+- 1 section -> 1 horizontal image
+- 4 sections -> 4 horizontal images
+- 8 sections -> 8 horizontal images
+- 12 sections -> 12 horizontal images
+
+Do not collapse multiple sections into one tall slice. Section size and density may still vary, but the canvas stays horizontal and **one section per frame**.
+
+### Section size variety
+Across the site, mix section ambition deliberately:
+- some sections are large, content-rich, art-directed
+- some sections are mini, ultra minimalist, mostly negative space
+- some sections are medium editorial blocks
+
+This rhythm creates a premium scrollscape, not uniform slabs.
+
+### Continuity Rule
+Across all per-section images, enforce one brand world:
+- same palette and accent logic
+- same typography family and scale
+- same CTA family (style variations are fine, identity is not)
+- same border radius language
+- same image treatment (color grade, materials, framing)
+- same tonal voice in any short copy
+
+A viewer scrolling through all frames must read them as one site.
+
+---
+
+## 6. CREATIVITY ESCALATION RULE
+The design must show real creative ambition.
+
+Do not settle for the first obvious layout solution.
+Push the work beyond generic SaaS patterns.
+
+Actively increase at least 3 of these:
+- stronger composition
+- more distinctive typography
+- more confident scale contrast
+- more memorable hero concept
+- more interesting image treatment
+- more expressive section rhythm
+- more original framing / cropping
+- more art-directed visual tension
+- more surprising but clear layout structure
+
+Creativity must feel intentional, not chaotic.
+
+Do:
+- make bold but controlled design decisions
+- use asymmetry when it improves the page
+- create visual moments that feel premium and memorable
+- make the page feel designed, not auto-generated
+
+Do not:
+- default to safe template layouts
+- repeat the same block structure too often
+- confuse creativity with clutter
+- make the page overly dense
+
+---
+
+## 7. IMAGE-FIRST ART DIRECTION
+This skill must actively use images.
+
+Images are not optional decoration.
+Images are a core part of the frontend design language.
+
+Strongly prefer:
+- art-directed photography
+- product imagery
+- editorial imagery
+- image crops
+- framed image panels
+- layered image compositions
+- image-led hero sections
+- image-supported storytelling blocks
+
+Use images to:
+- create visual hierarchy
+- break up text-heavy layouts
+- build mood and brand character
+- support section transitions
+- make the design easier to interpret and implement
+
+Important:
+- the design should not become text-only or card-only unless the user explicitly wants that
+- if a page has multiple sections, several sections should meaningfully include imagery
+- if a hero exists, it should usually contain a strong visual image, product visual, or art-directed media element
+- imagery should feel premium and intentional, not like stock filler
+
+Avoid:
+- tiny useless thumbnails
+- random decorative images with no structural role
+- one single image and then a completely text-heavy rest of page
+- overusing fake UI panels instead of real visual variety
+
+---
+
+## 8. ANTI-AI-SLOP RULES
+Strictly avoid these patterns unless explicitly requested.
+
+### Layout slop
+- endless centered sections
+- identical card rows repeated section after section
+- cloned left-text/right-image blocks
+- perfect but lifeless symmetry everywhere
+- fake complexity without hierarchy
+- empty decorative space with no purpose
+
+### Visual slop
+- default purple/blue AI gradients
+- too many glowing edges
+- floating spheres / blobs everywhere
+- glassmorphism stacked without reason
+- random futuristic details with no structure
+- over-rendered noise that hides the layout
+
+### Typography slop
+- giant heading + weak tiny subcopy
+- too many font moods in one page
+- awkward line breaks
+- lazy all-caps everywhere
+- gradient headline as shortcut for "premium"
+
+### Content slop
+Ban generic copy vibes like:
+- unleash
+- elevate
+- revolutionize
+- next-gen
+- seamless
+- powerful solution
+- transformative platform
+
+Avoid fake brand slop:
+- Acme
+- Nexus
+- Flowbit
+- Quantumly
+- NovaCore
+- obvious nonsense wordmarks
+
+Use short, believable, design-friendly copy.
+
+### Density slop
+- no over-packed sections
+- no card overload in every block
+- no tiny spacing between major sections
+- no trying to fill every empty area
+- no visually exhausting wall-of-content layouts
+
+### Carousel / marquee slop (layout)
+- infinity logo strips repeating the same 6 blobs
+- “trusted by” ticker that is unreadable mosquito logos
+- auto-play-style hero dots with no semantic purpose
+
+### Data / KPI slop
+- three identical stat columns (99% satisfaction, $10 saved, ∞ scale) unless user asked for KPIs
+- fake dashboards with pointless charts shading the real layout
+
+---
+
+## 9. TYPOGRAPHY-FIRST DISCIPLINE
+Typography is not filler.
+Typography is a primary design material.
+
+Always ensure:
+- clear size contrast
+- obvious reading order
+- strong display moments
+- supporting text that is readable and brief
+- labels, captions, and section headings that reinforce structure
+
+For editorial directions:
+- let typography shape composition
+
+For tech/product directions:
+- let typography communicate trust and precision
+
+---
+
+## 10. SECTION RHYTHM RULE
+A high-end site does not feel like repeated boxes.
+
+Vary section rhythm across the page by changing:
+- density
+- image-to-text ratio
+- alignment
+- scale
+- whitespace
+- card grouping
+- background intensity
+- visual tempo
+
+Do not let every section feel generated from the same template.
+
+Important:
+- rhythm variation should not break overall cleanliness
+- keep the page visually balanced from top to bottom
+- section heights may vary, but the spacing between sections should feel controlled and fairly even
+- avoid abrupt jumps between very small and very large sections without enough breathing room
+- the full page should feel curated, smooth, and consistent
+
+---
+
+## 11. COMPONENT EXECUTION GUIDELINES
+
+### Diagonal Staggered Square Masonry
+Use square image or content blocks with strong staggered vertical rhythm.
+Should feel curated and graphic, not messy.
+
+### 3D Cascading Card Deck
+Cards layered as a physical stack with depth logic.
+Should feel premium and tactile, not gimmicky.
+
+### Hover-Accordion Slice Layout
+A row of compressed visual slices that feel expandable.
+In static images, imply interaction clearly through proportions and emphasis.
+
+### Pristine Gapless Bento Grid
+Mathematically clean grid.
+No accidental gaps.
+Mix large visual blocks with smaller dense information panels.
+
+### Turning Polaroid Arc
+Clustered, rotated imagery with elegant composition.
+Should feel styled and intentional, not scrapbook-random.
+
+### Off-Grid Editorial Layout
+Use asymmetry and tension with control.
+Must remain readable and clearly structured.
+
+### Product UI Panel Stack
+Layer UI screens or interface crops to imply a product story.
+Avoid generic fake dashboards.
+
+### Vertical Rhythm Lines
+Use fine lines and spacing systems to reinforce order and elegance.
+Never let them become decorative clutter.
+
+---
+
+## 12. DENSITY & SPACING DISCIPLINE
+Do not make everything too dense.
+
+The page should breathe.
+Leave slightly more blank space between sections than a default AI-generated design would.
+
+Rules:
+- use more even vertical spacing between major sections
+- keep section-to-section spacing consistent unless there is a strong design reason not to
+- avoid one section feeling very cramped while the next feels too empty
+- prefer a clean, balanced cadence across the page
+- allow negative space to create rhythm and emphasis
+- separate denser sections with calmer sections
+- avoid stacking too many cards, labels, and content blocks too tightly
+- smaller sections should still receive enough surrounding space so the page feels polished and intentional
+
+A premium page should feel:
+- open
+- composed
+- balanced
+- confident
+- breathable
+
+Not:
+- cramped
+- noisy
+- uneven
+- overfilled
+- visually exhausted
+
+Section rhythm should alternate with control:
+- some sections can be more content-rich
+- some sections can be smaller and calmer
+- but the overall spacing cadence should still feel even, clean, and deliberate
+
+Whitespace is a design tool.
+Use it deliberately.
+Do not let spacing become random.
+
+---
+
+## 13. COLOR & MATERIAL RULES
+
+### Palette Discipline
+Use one controlled palette across the entire site:
+- 1 primary (brand anchor)
+- 1 secondary (supporting tone)
+- 1 accent (used sparingly for CTA / highlight)
+- a neutral scale (background, surface, text, hairline)
+
+Section-level mood shifts must reuse the same palette — no full theme swap per section.
+
+### Background-image harmony
+When using full-bleed image backgrounds:
+- the image must tonally match the palette (not fight it)
+- use overlays (dark, light, or color tint) to keep text fully readable
+- the brand accent stays consistent regardless of background image
+
+### Gradient Discipline
+Gradients are **allowed and encouraged** when professional and subtle. They are not the same as AI slop gradients.
+
+Allowed (use confidently):
+- low-chroma palette-matched tonal gradients (e.g. ink to graphite, cream to sand, ivory to warm grey)
+- single-hue atmospheric grades behind hero photography
+- soft vignettes and radial depth that direct the eye
+- noise-textured gradients adding tactile depth without color noise
+- editorial color washes that match brand mood
+
+Banned (AI gradient slop):
+- rainbow / mesh blob gradients
+- purple-to-blue "AI" defaults
+- pink-to-orange "creator" defaults
+- neon edges and glow halos with no purpose
+- gradient text as a shortcut for "premium"
+- gradients that compete with imagery instead of supporting it
+
+### Background Confidence Rule
+Do not retreat to plain white surfaces by default. When the brief, brand mood, or section job calls for atmosphere, use:
+- a full-bleed image,
+- a duotone or graded photo,
+- a tonal gradient,
+- a tactile material,
+or a confident flat color field — picked deliberately, not as decoration.
+
+### Strong guidance
+- avoid rainbow randomness
+- avoid over-neon unless requested
+- keep contrast intentional
+- match accent colors to the chosen theme paradigm
+- gradients must always read as professional and intentional, never as visual noise
+
+### Materiality
+Where appropriate, add:
+- paper feel
+- glass feel
+- brushed metal feel
+- soft blur depth
+- tactile matte surfaces
+- editorial photo treatment
+
+But always keep the frontend structure readable.
+
+---
+
+## 14. IMAGE / MEDIA DIRECTION
+If imagery is present, it must support the layout.
+
+Allowed:
+- art-directed product visuals
+- refined editorial photography
+- UI crops
+- abstract forms with structural purpose
+- framed objects
+- premium texture use
+- campaign-style visuals
+
+Avoid:
+- irrelevant scenery
+- stock-photo cliches
+- decorative junk
+- visuals that overpower the page hierarchy
+
+---
+
+## 15. DEFAULT SITE PACKS
+
+### 4-section pack
+1. Hero
+2. Features
+3. Social proof / testimonial
+4. CTA
+
+### 8-section pack
+1. Hero
+2. Trust bar
+3. Features
+4. Product showcase
+5. Benefits / use cases
+6. Testimonials
+7. Pricing
+8. CTA
+
+### 12-section pack
+1. Hero
+2. Trust bar
+3. Feature grid
+4. Product preview
+5. Problem / solution
+6. Benefits
+7. Workflow
+8. Metrics / proof / integration
+9. Testimonials
+10. Pricing
+11. FAQ
+12. CTA + footer
+
+---
+
+## 16. MULTI-IMAGE CONSISTENCY RULE
+Because every section is its own image, consistency is critical. Across all per-section frames enforce:
+- same brand world
+- same type scale logic
+- same spacing discipline
+- same CTA family (style variations are fine, identity is not)
+- same icon or illustration mood
+- same image treatment (grade, framing, material vocabulary)
+- same tonal language in any copy
+
+Variation IS allowed in:
+- composition anchor (per section)
+- background mode (per section)
+- section size and density
+- which "second-read" moment appears
+
+A viewer flipping through every per-section frame must still recognize one brand. Anything that breaks brand recall is over-variation.
+
+---
+
+## 17. CLARITY CHECK
+Before finalizing, verify internally:
+
+1. Is the hierarchy obvious?
+2. Is the hero clean enough?
+3. Is the design visually distinctive?
+4. Is it free of obvious AI tells?
+5. Is it premium rather than template-like?
+6. Can someone code from this?
+7. If multiple images exist, do they clearly belong together?
+8. Is imagery used strongly enough (with variation, not one repeated crop)?
+9. Does the page breathe, or is it too dense?
+10. Is there enough spacing between sections?
+11. Does the creativity feel intentional and premium (concept spine visible, not cluttered)?
+12. Is the spacing between sections even and controlled?
+13. Do smaller sections still have enough surrounding space to feel clean?
+14. Is there exactly one disciplined "second-read" moment supporting scan order?
+15. Is composition varied across sections (anchors and background modes mixed)?
+16. Is the hero scale (giant / mid / mini) chosen and executed cleanly?
+17. Is there a clear conversion path (hook -> proof -> action) even in artistic sites?
+18. Is the palette consistent across all per-section images?
+19. Is each image horizontal and one-section-only?
+20. Is the **total number of images equal to the number of sections** (never fewer)?
+21. Is the hero using a varied composition (not defaulting to left-text / right-image out of habit)?
+
+If not, refine internally before output. If the count is wrong, regenerate the missing sections. If the hero feels like a reflexive left-text / right-image default, prefer a different composition anchor.
+
+---
+
+## 18. EXTRA CREATIVITY & IMPLEMENTATION EDGE
+
+Apply unless the user opts out:
+
+### Cross-section contrast
+Across the slice, deliberately vary foreground/background intensity at least twice (lighter → richer → calmer) so the scroll feels paced, not monotonous slabs.
+
+### CTA specificity
+Prefer one unmistakable primary action per major viewport tier; secondary actions must look secondary (scale, outline, ghost), not clones of primary.
+
+### Image variety inside one comp
+Mix at least **two distinct image crops** where multiple sections exist — e.g. macro product + contextual environment, or portrait editorial + widescreen artifact — avoiding one repeated stock silhouette.
+
+### Data-viz restraint
+Charts, sparklines, and graphs appear only when the site type logically needs them (analytics, pricing, infra, observability brands). Else keep proof human (quotes, receipts, timelines, screenshots of real workflows).
+
+### Cultural / tonal alignment
+When the brief names an industry or region, steer palette and typographic temperament to match — don’t ship default “neutral SF startup” unless the brief is intentionally generic SaaS.
+
+### Mobile-implied fidelity (even for desktop mocks)
+Maintain tap-friendly hit sizes and readable caption sizes visually; stacking order should imply a sane single-column narrative.
+
+### Conversion focus
+Each section has a job. Even when the design is artistic, the page must read as a real product or brand site:
+- the hero communicates value in seconds and offers one obvious next action
+- proof sections (logos, quotes, metrics) feel earned, not stuffed
+- pricing or CTA sections feel decisive, not buried
+- the final section closes: a single strong CTA + supporting trust cue
+Avoid pure mood reels with no funnel logic.
+
+### Composition variety check
+Across all per-section images, internally log the chosen composition anchor and background mode. Reject the set if:
+- the same composition anchor repeats more than 2 sections in a row
+- the same background mode repeats more than 3 sections in a row
+- every section is inline-asset (no full-bleed background ever appears) **AND** the brief does not call for minimalism / typography-only / swiss / ultra simple
+
+For non-minimalist briefs: push for at least one full-bleed (or duotone / atmospheric) background and at least one mini minimalist section in any multi-section site.
+
+For minimalist briefs: this rule is suspended. Restraint is the design.
+
+---
+
+## 19. RESPONSE BEHAVIOR
+When the user asks for a frontend design:
+1. infer site type and primary conversion goal
+2. infer number of sections (if unclear, use the defaults from §5: landing page = 6, full website = 8)
+3. **commit out loud** to the section count and announce it ("Generating N horizontal images, one per section")
+4. plan ONE horizontal image PER SECTION — always separate generations, never collapse
+5. choose Hero Scale for the whole site (giant / mid / mini)
+5. choose a strong visual combination (theme, type, hero arch, section system, motion, narrative spine, second-read moment)
+7. for each section: pick a Composition Anchor, Background Mode, and CTA Variation — vary across sections
+8. choose 4 signature components used appropriately across sections
+9. enforce hero minimalism + section size variety (some giant, some mini)
+10. enforce strong image usage including full-bleed backgrounds where it fits
+11. lock one consistent palette across all images
+12. apply §18 EXTRA CREATIVITY & IMPLEMENTATION EDGE
+13. keep spacing generous, even, and clean
+14. remove AI slop (including marquee / fake KPI clichés unless requested)
+15. run §17 CLARITY CHECK
+16. **generate every per-section horizontal image, labeled "Section X of N: <name>"**, until the full set is delivered. Do not stop early. Do not summarize. Do not return only one image.
+
+Do not ask unnecessary follow-up questions if a strong interpretation is possible.
+
+---
+
+## 20. EXAMPLE INTERPRETATIONS
+
+### Example 1
+User: "make a hero section for an AI startup"
+
+Interpretation:
+- 1 horizontal image
+- Hero Scale: Mid Editorial or Giant Statement
+- Composition Anchor: bottom-left text over full-bleed product/atmosphere image
+- Background Mode: full-bleed image with dark tonal overlay
+- CTA Variation: outlined inline + small label hint
+- Palette: Deep Dark or Bold Studio Solid, one consistent accent
+- no cliche dashboard spam, no purple AI glow
+
+### Example 2
+User: "design 8 sections for a fintech website"
+
+Interpretation:
+- 8 separate horizontal images (one per section)
+- Hero Scale: Mid Editorial (trust-driven)
+- vary Composition Anchor across sections (centered low, right-third caption, bottom-left over chart visual, stacked center for closing CTA)
+- Background Mode mix: solid surface, full-bleed image background once, editorial side-image at use cases
+- one consistent palette (e.g. ink + paper + single brand accent)
+- conversion path: hook -> proof bar -> features -> use case -> testimonial -> pricing -> FAQ -> final CTA
+
+### Example 3
+User: "creative agency landing page, 12 sections"
+
+Interpretation:
+- 12 horizontal images (one per section)
+- Hero Scale: Giant Statement OR Mini Minimalist (decisive choice, not in-between)
+- editorial / poster-like direction; off-grid composition appears 2-3 times
+- multiple Background Modes (full-bleed image at hero + showcase, editorial side-image at case studies, solid + accent for process)
+- palette consistent throughout, with one bold accent recurring
+- closing CTA section: mini minimalist, strong type, single primary action
+
+---
+
+## 21. FINAL GOAL
+Generate frontend reference images that feel:
+- artistic
+- premium
+- clear
+- structured
+- image-led
+- breathable
+- memorable
+- anti-generic
+- implementation-friendly
+
+The result should look like a top-tier website concept with strong imagery, confident creativity, and generous spacing - not a dense, repetitive AI layout.

.agents/skills/industrial-brutalist-ui/SKILL.md

@@ -0,0 +1,92 @@
+---
+name: industrial-brutalist-ui
+description: Raw mechanical interfaces fusing Swiss typographic print with military terminal aesthetics. Rigid grids, extreme type scale contrast, utilitarian color, analog degradation effects. For data-heavy dashboards, portfolios, or editorial sites that need to feel like declassified blueprints.
+---
+
+# SKILL: Industrial Brutalism & Tactical Telemetry UI
+
+## 1. Skill Meta
+**Name:** Industrial Brutalism & Tactical Telemetry Interface Engineering
+**Description:** Advanced proficiency in architecting web interfaces that synthesize mid-century Swiss Typographic design, industrial manufacturing manuals, and retro-futuristic aerospace/military terminal interfaces. This discipline requires absolute mastery over rigid modular grids, extreme typographic scale contrast, purely utilitarian color palettes, and the programmatic simulation of analog degradation (halftones, CRT scanlines, bitmap dithering). The objective is to construct digital environments that project raw functionality, mechanical precision, and high data density, deliberately discarding conventional consumer UI patterns.
+
+## 2. Visual Archetypes
+The design system operates by merging two distinct but highly compatible visual paradigms. **Pick ONE per project and commit to it. Do not alternate or mix both modes within the same interface.**
+
+### 2.1 Swiss Industrial Print
+Derived from 1960s corporate identity systems and heavy machinery blueprints.
+*   **Characteristics:** High-contrast light modes (newsprint/off-white substrates). Reliance on monolithic, heavy sans-serif typography. Unforgiving structural grids outlined by visible dividing lines. Aggressive, asymmetric use of negative space punctuated by oversized, viewport-bleeding numerals or letterforms. Heavy use of primary red as an alert/accent color.
+
+### 2.2 Tactical Telemetry & CRT Terminal
+Derived from classified military databases, legacy mainframes, and aerospace Heads-Up Displays (HUDs).
+*   **Characteristics:** Dark mode exclusivity. High-density tabular data presentation. Absolute dominance of monospaced typography. Integration of technical framing devices (ASCII brackets, crosshairs). Application of simulated hardware limitations (phosphor glow, scanlines, low bit-depth rendering).
+
+## 3. Typographic Architecture
+Typography is the primary structural and decorative infrastructure. Imagery is secondary. The system demands extreme variance in scale, weight, and spacing.
+
+### 3.1 Macro-Typography (Structural Headers)
+*   **Classification:** Neo-Grotesque / Heavy Sans-Serif.
+*   **Optimal Web Fonts:** Neue Haas Grotesk (Black), Inter (Extra Bold/Black), Archivo Black, Roboto Flex (Heavy), Monument Extended.
+*   **Implementation Parameters:**
+    *   **Scale:** Deployed at massive scales using fluid typography (e.g., `clamp(4rem, 10vw, 15rem)`).
+    *   **Tracking (Letter-spacing):** Extremely tight, often negative (`-0.03em` to `-0.06em`), forcing glyphs to form solid architectural blocks.
+    *   **Leading (Line-height):** Highly compressed (`0.85` to `0.95`).
+    *   **Casing:** Exclusively uppercase for structural impact.
+
+### 3.2 Micro-Typography (Data & Telemetry)
+*   **Classification:** Monospace / Technical Sans.
+*   **Optimal Web Fonts:** JetBrains Mono, IBM Plex Mono, Space Mono, VT323, Courier Prime.
+*   **Implementation Parameters:**
+    *   **Scale:** Fixed and small (`10px` to `14px` / `0.7rem` to `0.875rem`).
+    *   **Tracking:** Generous (`0.05em` to `0.1em`) to simulate mechanical typewriter spacing or terminal matrices.
+    *   **Leading:** Standard to tight (`1.2` to `1.4`).
+    *   **Casing:** Exclusively uppercase. Used for all metadata, navigation, unit IDs, and coordinates.
+
+### 3.3 Textural Contrast (Artistic Disruption)
+*   **Classification:** High-Contrast Serif.
+*   **Optimal Web Fonts:** Playfair Display, EB Garamond, Times New Roman.
+*   **Implementation Parameters:** Used exceedingly sparingly. Must be subjected to heavy post-processing (halftone filters, 1-bit dithering) to degrade vector perfection and create textural juxtaposition against the clean sans-serifs.
+
+## 4. Color System
+The color architecture is uncompromising. Gradients, soft drop shadows, and modern translucency are strictly prohibited. Colors simulate physical media or primitive emissive displays.
+
+**CRITICAL: Choose ONE substrate palette per project and use it consistently. Never mix light and dark substrates within the same interface.**
+
+### If Swiss Industrial Print (Light):
+*   **Background:** `#F4F4F0` or `#EAE8E3` (Matte, unbleached documentation paper).
+*   **Foreground:** `#050505` to `#111111` (Carbon Ink).
+*   **Accent:** `#E61919` or `#FF2A2A` (Aviation/Hazard Red). This is the ONLY accent color. Used for strike-throughs, thick structural dividing lines, or vital data highlights.
+
+### If Tactical Telemetry (Dark):
+*   **Background:** `#0A0A0A` or `#121212` (Deactivated CRT. Avoid pure `#000000`).
+*   **Foreground:** `#EAEAEA` (White phosphor). This is the primary text color.
+*   **Accent:** `#E61919` or `#FF2A2A` (Aviation/Hazard Red). Same red, same rules.
+*   **Terminal Green (`#4AF626`):** Optional. Use ONLY for a single specific UI element (e.g., one status indicator or one data readout) — never as a general text color. If it doesn't serve a clear purpose, omit it entirely.
+
+## 5. Layout and Spatial Engineering
+The layout must appear mathematically engineered. It rejects conventional web padding in favor of visible compartmentalization.
+
+*   **The Blueprint Grid:** Strict adherence to CSS Grid architectures. Elements do not float; they are anchored precisely to grid tracks and intersections.
+*   **Visible Compartmentalization:** Extensive utilization of solid borders (`1px` or `2px solid`) to delineate distinct zones of information. Horizontal rules (`<hr>`) frequently span the entire container width to segregate operational units.
+*   **Bimodal Density:** Layouts oscillate between extreme data density (tightly packed monospace metadata clustered together) and vast expanses of calculated negative space framing macro-typography.
+*   **Geometry:** Absolute rejection of `border-radius`. All corners must be exactly 90 degrees to enforce mechanical rigidity.
+
+## 6. UI Components and Symbology
+Standard web UI conventions are replaced with utilitarian, industrial graphic elements.
+
+*   **Syntax Decoration:** Utilization of ASCII characters to frame data points.
+    *   *Framing:* `[ DELIVERY SYSTEMS ]`, `< RE-IND >`
+    *   *Directional:* `>>>`, `///`, `\\\\`
+*   **Industrial Markers:** Prominent integration of registration (`®`), copyright (`©`), and trademark (`™`) symbols functioning as structural geometric elements rather than legal text.
+*   **Technical Assets:** Integration of crosshairs (`+`) at grid intersections, repeating vertical lines (barcodes), thick horizontal warning stripes, and randomized string data (e.g., `REV 2.6`, `UNIT / D-01`) to simulate active mechanical processes.
+
+## 7. Textural and Post-Processing Effects
+To prevent the design from appearing purely digital, simulated analog degradation is engineered into the frontend via CSS and SVG filters.
+
+*   **Halftone and 1-Bit Dithering:** Transforming continuous-tone images or large serif typography into dot-matrix patterns. Achieved via pre-processing or CSS `mix-blend-mode: multiply` overlays combined with SVG radial dot patterns.
+*   **CRT Scanlines:** For terminal interfaces, applying a `repeating-linear-gradient` to the background to simulate horizontal electron beam sweeps (e.g., `repeating-linear-gradient(0deg, transparent, transparent 2px, rgba(0,0,0,0.1) 2px, rgba(0,0,0,0.1) 4px)`).
+*   **Mechanical Noise:** A global, low-opacity SVG static/noise filter applied to the DOM root to introduce a unified physical grain across both dark and light modes.
+
+## 8. Web Engineering Directives
+1.  **Grid Determinism:** Utilize `display: grid; gap: 1px;` with contrasting parent/child background colors to generate mathematically perfect, razor-thin dividing lines without complex border declarations.
+2.  **Semantic Rigidity:** Construct the DOM using precise semantic tags (`<data>`, `<samp>`, `<kbd>`, `<output>`, `<dl>`) to accurately reflect the technical nature of the telemetry.
+3.  **Typography Clamping:** Implement CSS `clamp()` functions exclusively for macro-typography to ensure massive text scales aggressively while maintaining structural integrity across viewports.

.agents/skills/minimalist-ui/SKILL.md

@@ -0,0 +1,85 @@
+---
+name: minimalist-ui
+description: Clean editorial-style interfaces. Warm monochrome palette, typographic contrast, flat bento grids, muted pastels. No gradients, no heavy shadows.
+---
+
+# Protocol: Premium Utilitarian Minimalism UI Architect
+
+## 1. Protocol Overview
+Name: Premium Utilitarian Minimalism & Editorial UI
+Description: An advanced frontend engineering directive for generating highly refined, ultra-minimalist, "document-style" web interfaces analogous to top-tier workspace platforms. This protocol strictly enforces a high-contrast warm monochrome palette, bespoke typographic hierarchies, meticulous structural macro-whitespace, bento-grid layouts, and an ultra-flat component architecture with deliberate muted pastel accents. It actively rejects standard generic SaaS design trends.
+
+## 2. Absolute Negative Constraints (Banned Elements)
+The AI must strictly avoid the following generic web development defaults:
+- DO NOT use the "Inter", "Roboto", or "Open Sans" typefaces.
+- DO NOT use generic, thin-line icon libraries like "Lucide", "Feather", or standard "Heroicons".
+- DO NOT use Tailwind's default heavy drop shadows (e.g., `shadow-md`, `shadow-lg`, `shadow-xl`). Shadows must be practically non-existent or heavily customized to be ultra-diffuse and low opacity (< 0.05).
+- DO NOT use primary colored backgrounds for large elements or sections (e.g., no bright blue, green, or red hero sections).
+- DO NOT use gradients, neon colors, or 3D glassmorphism (beyond subtle navbar blurs).
+- DO NOT use `rounded-full` (pill shapes) for large containers, cards, or primary buttons.
+- DO NOT use emojis anywhere in code, markup, text content, headings, or alt text. Replace with proper icons or clean SVG primitives.
+- DO NOT use generic placeholder names like "John Doe", "Acme Corp", or "Lorem Ipsum". Use realistic, contextual content.
+- DO NOT use AI copywriting clichés: "Elevate", "Seamless", "Unleash", "Next-Gen", "Game-changer", "Delve". Write plain, specific language.
+
+## 3. Typographic Architecture
+The interface must rely on extreme typographic contrast and premium font selection to establish an editorial feel.
+- Primary Sans-Serif (Body, UI, Buttons): Use clean, geometric, or system-native fonts with character. Target: `font-family: 'SF Pro Display', 'Geist Sans', 'Helvetica Neue', 'Switzer', sans-serif`.
+- Editorial Serif (Hero Headings & Quotes): Target: `font-family: 'Lyon Text', 'Newsreader', 'Playfair Display', 'Instrument Serif', serif`. Apply tight tracking (`letter-spacing: -0.02em` to `-0.04em`) and tight line-height (`1.1`).
+- Monospace (Code, Keystrokes, Meta-data): Target: `font-family: 'Geist Mono', 'SF Mono', 'JetBrains Mono', monospace`.
+- Text Colors: Body text must never be absolute black (`#000000`). Use off-black/charcoal (`#111111` or `#2F3437`) with a generous `line-height` of `1.6` for legibility. Secondary text should be muted gray (`#787774`).
+
+## 4. Color Palette (Warm Monochrome + Spot Pastels)
+Color is a scarce resource, utilized only for semantic meaning or subtle accents.
+- Canvas / Background: Pure White `#FFFFFF` or Warm Bone/Off-White `#F7F6F3` / `#FBFBFA`.
+- Primary Surface (Cards): `#FFFFFF` or `#F9F9F8`.
+- Structural Borders / Dividers: Ultra-light gray `#EAEAEA` or `rgba(0,0,0,0.06)`.
+- Accent Colors: Exclusively use highly desaturated, washed-out pastels for tags, inline code backgrounds, or subtle icon backgrounds.
+  - Pale Red: `#FDEBEC` (Text: `#9F2F2D`)
+  - Pale Blue: `#E1F3FE` (Text: `#1F6C9F`)
+  - Pale Green: `#EDF3EC` (Text: `#346538`)
+  - Pale Yellow: `#FBF3DB` (Text: `#956400`)
+
+## 5. Component Specifications
+- Bento Box Feature Grids:
+  - Utilize asymmetrical CSS Grid layouts.
+  - Cards must have exactly `border: 1px solid #EAEAEA`.
+  - Border-radius must be crisp: `8px` or `12px` maximum.
+  - Internal padding must be generous (e.g., `24px` to `40px`).
+- Primary Call-To-Action (Buttons):
+  - Solid background `#111111`, text `#FFFFFF`. 
+  - Slight border-radius (`4px` to `6px`). No box-shadow. 
+  - Hover state should be a subtle color shift to `#333333` or a micro-scale `transform: scale(0.98)`.
+- Tags & Status Badges:
+  - Pill-shaped (`border-radius: 9999px`), very small typography (`text-xs`), uppercase with wide tracking (`letter-spacing: 0.05em`).
+  - Background must use the defined Muted Pastels.
+- Accordions (FAQ):
+  - Strip all container boxes. Separate items only with a `border-bottom: 1px solid #EAEAEA`.
+  - Use a clean, sharp `+` and `-` icon for the toggle state.
+- Keystroke Micro-UIs:
+  - Render shortcuts as physical keys using `<kbd>` tags: `border: 1px solid #EAEAEA`, `border-radius: 4px`, `background: #F7F6F3`, using the Monospace font.
+- Faux-OS Window Chrome:
+  - When mocking up software, wrap it in a minimalist container with a white top bar containing three small, light gray circles (replicating macOS window controls).
+
+## 6. Iconography & Imagery Directives
+- System Icons: Use "Phosphor Icons (Bold or Fill weights)" or "Radix UI Icons" for a technical, slightly thicker-stroke aesthetic. Standardize stroke width across all icons.
+- Illustrations: Monochromatic, rough continuous-line ink sketches on a white background, featuring a single offset geometric shape filled with a muted pastel color.
+- Photography: Use high-quality, desaturated images with a warm tone. Apply subtle overlays (`opacity: 0.04` warm grain) to blend photos into the monochrome palette. Never use oversaturated stock photos. Use reliable placeholders like `https://picsum.photos/seed/{context}/1200/800` when real assets are unavailable.
+- Hero & Section Backgrounds: Sections should not feel empty and flat. Use subtle full-width background imagery at very low opacity, soft radial light spots (`radial-gradient` with warm tones at `opacity: 0.03`), or minimal geometric line patterns to add depth without breaking the clean aesthetic.
+
+## 7. Subtle Motion & Micro-Animations
+Motion should feel invisible — present but never distracting. The goal is quiet sophistication, not spectacle.
+- Scroll Entry: Elements fade in gently as they enter the viewport. Use `translateY(12px)` + `opacity: 0` resolving over `600ms` with `cubic-bezier(0.16, 1, 0.3, 1)`. Use `IntersectionObserver`, never `window.addEventListener('scroll')`.
+- Hover States: Cards lift with an ultra-subtle shadow shift (`box-shadow` transitioning from `0 0 0` to `0 2px 8px rgba(0,0,0,0.04)` over `200ms`). Buttons respond with `scale(0.98)` on `:active`.
+- Staggered Reveals: Lists and grid items enter with a cascade delay (`animation-delay: calc(var(--index) * 80ms)`). Never mount everything at once.
+- Background Ambient Motion: Optional. A single, very slow-moving radial gradient blob (`animation-duration: 20s+`, `opacity: 0.02-0.04`) drifting behind hero sections. Must be applied to a `position: fixed; pointer-events: none` layer. Never on scrolling containers.
+- Performance: Animate exclusively via `transform` and `opacity`. No layout-triggering properties (`top`, `left`, `width`, `height`). Use `will-change: transform` sparingly and only on actively animating elements.
+
+## 8. Execution Protocol
+When tasked with writing frontend code (HTML, React, Tailwind, Vue) or designing a layout:
+1. Establish the macro-whitespace first. Use massive vertical padding between sections (e.g., `py-24` or `py-32` in Tailwind).
+2. Constrain the main typography content width to `max-w-4xl` or `max-w-5xl`.
+3. Apply the custom typographic hierarchy and monochromatic color variables immediately.
+4. Ensure every card, divider, and border adheres strictly to the `1px solid #EAEAEA` rule.
+5. Add scroll-entry animations to all major content blocks.
+6. Ensure sections have visual depth through imagery, ambient gradients, or subtle textures — no empty flat backgrounds.
+7. Provide code that reflects this high-end, uncluttered, editorial aesthetic natively without requiring manual adjustments.

.agents/skills/redesign-existing-projects/SKILL.md

@@ -0,0 +1,178 @@
+---
+name: redesign-existing-projects
+description: Upgrades existing websites and apps to premium quality. Audits current design, identifies generic AI patterns, and applies high-end design standards without breaking functionality. Works with any CSS framework or vanilla CSS.
+---
+
+# Redesign Skill
+
+## How This Works
+
+When applied to an existing project, follow this sequence:
+
+1. **Scan** — Read the codebase. Identify the framework, styling method (Tailwind, vanilla CSS, styled-components, etc.), and current design patterns.
+2. **Diagnose** — Run through the audit below. List every generic pattern, weak point, and missing state you find.
+3. **Fix** — Apply targeted upgrades working with the existing stack. Do not rewrite from scratch. Improve what's there.
+
+## Design Audit
+
+### Typography
+
+Check for these problems and fix them:
+
+- **Browser default fonts or Inter everywhere.** Replace with a font that has character. Good options: `Geist`, `Outfit`, `Cabinet Grotesk`, `Satoshi`. For editorial/creative projects, pair a serif header with a sans-serif body.
+- **Headlines lack presence.** Increase size for display text, tighten letter-spacing, reduce line-height. Headlines should feel heavy and intentional.
+- **Body text too wide.** Limit paragraph width to roughly 65 characters. Increase line-height for readability.
+- **Only Regular (400) and Bold (700) weights used.** Introduce Medium (500) and SemiBold (600) for more subtle hierarchy.
+- **Numbers in proportional font.** Use a monospace font or enable tabular figures (`font-variant-numeric: tabular-nums`) for data-heavy interfaces.
+- **Missing letter-spacing adjustments.** Use negative tracking for large headers, positive tracking for small caps or labels.
+- **All-caps subheaders everywhere.** Try lowercase italics, sentence case, or small-caps instead.
+- **Orphaned words.** Single words sitting alone on the last line. Fix with `text-wrap: balance` or `text-wrap: pretty`.
+
+### Color and Surfaces
+
+- **Pure `#000000` background.** Replace with off-black, dark charcoal, or tinted dark (`#0a0a0a`, `#121212`, or a dark navy).
+- **Oversaturated accent colors.** Keep saturation below 80%. Desaturate accents so they blend with neutrals instead of screaming.
+- **More than one accent color.** Pick one. Remove the rest. Consistency beats variety.
+- **Mixing warm and cool grays.** Stick to one gray family. Tint all grays with a consistent hue (warm or cool, not both).
+- **Purple/blue "AI gradient" aesthetic.** This is the most common AI design fingerprint. Replace with neutral bases and a single, considered accent.
+- **Generic `box-shadow`.** Tint shadows to match the background hue. Use colored shadows (e.g., dark blue shadow on a blue background) instead of pure black at low opacity.
+- **Flat design with zero texture.** Add subtle noise, grain, or micro-patterns to backgrounds. Pure flat vectors feel sterile.
+- **Perfectly even gradients.** Break the uniformity with radial gradients, noise overlays, or mesh gradients instead of standard linear 45-degree fades.
+- **Inconsistent lighting direction.** Audit all shadows to ensure they suggest a single, consistent light source.
+- **Random dark sections in a light mode page (or vice versa).** A single dark-background section breaking an otherwise light page looks like a copy-paste accident. Either commit to a full dark mode or keep a consistent background tone throughout. If contrast is needed, use a slightly darker shade of the same palette — not a sudden jump to `#111` in the middle of a cream page.
+- **Empty, flat sections with no visual depth.** Sections that are just text on a plain background feel unfinished. Add high-quality background imagery (blurred, overlaid, or masked), subtle patterns, or ambient gradients. Use reliable placeholder sources like `https://picsum.photos/seed/{name}/1920/1080` when real assets are not available. Experiment with background images behind hero sections, feature blocks, or CTAs — even a subtle full-width photo at low opacity adds presence.
+
+### Layout
+
+- **Everything centered and symmetrical.** Break symmetry with offset margins, mixed aspect ratios, or left-aligned headers over centered content.
+- **Three equal card columns as feature row.** This is the most generic AI layout. Replace with a 2-column zig-zag, asymmetric grid, horizontal scroll, or masonry layout.
+- **Using `height: 100vh` for full-screen sections.** Replace with `min-height: 100dvh` to prevent layout jumping on mobile browsers (iOS Safari viewport bug).
+- **Complex flexbox percentage math.** Replace with CSS Grid for reliable multi-column structures.
+- **No max-width container.** Add a container constraint (around 1200-1440px) with auto margins so content doesn't stretch edge-to-edge on wide screens.
+- **Cards of equal height forced by flexbox.** Allow variable heights or use masonry when content varies in length.
+- **Uniform border-radius on everything.** Vary the radius: tighter on inner elements, softer on containers.
+- **No overlap or depth.** Elements sit flat next to each other. Use negative margins to create layering and visual depth.
+- **Symmetrical vertical padding.** Top and bottom padding are always identical. Adjust optically — bottom padding often needs to be slightly larger.
+- **Dashboard always has a left sidebar.** Try top navigation, a floating command menu, or a collapsible panel instead.
+- **Missing whitespace.** Double the spacing. Let the design breathe. Dense layouts work for data dashboards, not for marketing pages.
+- **Buttons not bottom-aligned in card groups.** When cards have different content lengths, CTAs end up at random heights. Pin buttons to the bottom of each card so they form a clean horizontal line regardless of content above.
+- **Feature lists starting at different vertical positions.** In pricing tables or comparison cards, the list of features should start at the same Y position across all columns. Use consistent spacing above the list or fixed-height title/price blocks.
+- **Inconsistent vertical rhythm in side-by-side elements.** When placing cards, columns, or panels next to each other, align shared elements (titles, descriptions, prices, buttons) across all items. Misaligned baselines make the layout look broken.
+- **Mathematical alignment that looks optically wrong.** Centering by the math doesn't always look centered to the eye. Icons next to text, play buttons in circles, or text in buttons often need 1-2px optical adjustments to feel right.
+
+### Interactivity and States
+
+- **No hover states on buttons.** Add background shift, slight scale, or translate on hover.
+- **No active/pressed feedback.** Add a subtle `scale(0.98)` or `translateY(1px)` on press to simulate a physical click.
+- **Instant transitions with zero duration.** Add smooth transitions (200-300ms) to all interactive elements.
+- **Missing focus ring.** Ensure visible focus indicators for keyboard navigation. This is an accessibility requirement, not optional.
+- **No loading states.** Replace generic circular spinners with skeleton loaders that match the layout shape.
+- **No empty states.** An empty dashboard showing nothing is a missed opportunity. Design a composed "getting started" view.
+- **No error states.** Add clear, inline error messages for forms. Do not use `window.alert()`.
+- **Dead links.** Buttons that link to `#`. Either link to real destinations or visually disable them.
+- **No indication of current page in navigation.** Style the active nav link differently so users know where they are.
+- **Scroll jumping.** Anchor clicks jump instantly. Add `scroll-behavior: smooth`.
+- **Animations using `top`, `left`, `width`, `height`.** Switch to `transform` and `opacity` for GPU-accelerated, smooth animation.
+
+### Content
+
+- **Generic names like "John Doe" or "Jane Smith".** Use diverse, realistic-sounding names.
+- **Fake round numbers like `99.99%`, `50%`, `$100.00`.** Use organic, messy data: `47.2%`, `$99.00`, `+1 (312) 847-1928`.
+- **Placeholder company names like "Acme Corp", "Nexus", "SmartFlow".** Invent contextual, believable brand names.
+- **AI copywriting cliches.** Never use "Elevate", "Seamless", "Unleash", "Next-Gen", "Game-changer", "Delve", "Tapestry", or "In the world of...". Write plain, specific language.
+- **Exclamation marks in success messages.** Remove them. Be confident, not loud.
+- **"Oops!" error messages.** Be direct: "Connection failed. Please try again."
+- **Passive voice.** Use active voice: "We couldn't save your changes" instead of "Mistakes were made."
+- **All blog post dates identical.** Randomize dates to appear real.
+- **Same avatar image for multiple users.** Use unique assets for every distinct person.
+- **Lorem Ipsum.** Never use placeholder latin text. Write real draft copy.
+- **Title Case On Every Header.** Use sentence case instead.
+
+### Component Patterns
+
+- **Generic card look (border + shadow + white background).** Remove the border, or use only background color, or use only spacing. Cards should exist only when elevation communicates hierarchy.
+- **Always one filled button + one ghost button.** Add text links or tertiary styles to reduce visual noise.
+- **Pill-shaped "New" and "Beta" badges.** Try square badges, flags, or plain text labels.
+- **Accordion FAQ sections.** Use a side-by-side list, searchable help, or inline progressive disclosure.
+- **3-card carousel testimonials with dots.** Replace with a masonry wall, embedded social posts, or a single rotating quote.
+- **Pricing table with 3 towers.** Highlight the recommended tier with color and emphasis, not just extra height.
+- **Modals for everything.** Use inline editing, slide-over panels, or expandable sections instead of popups for simple actions.
+- **Avatar circles exclusively.** Try squircles or rounded squares for a less generic look.
+- **Light/dark toggle always a sun/moon switch.** Use a dropdown, system preference detection, or integrate it into settings.
+- **Footer link farm with 4 columns.** Simplify. Focus on main navigational paths and legally required links.
+
+### Iconography
+
+- **Lucide or Feather icons exclusively.** These are the "default" AI icon choice. Use Phosphor, Heroicons, or a custom set for differentiation.
+- **Rocketship for "Launch", shield for "Security".** Replace cliche metaphors with less obvious icons (bolt, fingerprint, spark, vault).
+- **Inconsistent stroke widths across icons.** Audit all icons and standardize to one stroke weight.
+- **Missing favicon.** Always include a branded favicon.
+- **Stock "diverse team" photos.** Use real team photos, candid shots, or a consistent illustration style instead of uncanny stock imagery.
+
+### Code Quality
+
+- **Div soup.** Use semantic HTML: `<nav>`, `<main>`, `<article>`, `<aside>`, `<section>`.
+- **Inline styles mixed with CSS classes.** Move all styling to the project's styling system.
+- **Hardcoded pixel widths.** Use relative units (`%`, `rem`, `em`, `max-width`) for flexible layouts.
+- **Missing alt text on images.** Describe image content for screen readers. Never leave `alt=""` or `alt="image"` on meaningful images.
+- **Arbitrary z-index values like `9999`.** Establish a clean z-index scale in the theme/variables.
+- **Commented-out dead code.** Remove all debug artifacts before shipping.
+- **Import hallucinations.** Check that every import actually exists in `package.json` or the project dependencies.
+- **Missing meta tags.** Add proper `<title>`, `description`, `og:image`, and social sharing meta tags.
+
+### Strategic Omissions (What AI Typically Forgets)
+
+- **No legal links.** Add privacy policy and terms of service links in the footer.
+- **No "back" navigation.** Dead ends in user flows. Every page needs a way back.
+- **No custom 404 page.** Design a helpful, branded "page not found" experience.
+- **No form validation.** Add client-side validation for emails, required fields, and format checks.
+- **No "skip to content" link.** Essential for keyboard users. Add a hidden skip-link.
+- **No cookie consent.** If required by jurisdiction, add a compliant consent banner.
+
+## Upgrade Techniques
+
+When upgrading a project, pull from these high-impact techniques to replace generic patterns:
+
+### Typography Upgrades
+- **Variable font animation.** Interpolate weight or width on scroll or hover for text that feels alive.
+- **Outlined-to-fill transitions.** Text starts as a stroke outline and fills with color on scroll entry or interaction.
+- **Text mask reveals.** Large typography acting as a window to video or animated imagery behind it.
+
+### Layout Upgrades
+- **Broken grid / asymmetry.** Elements that deliberately ignore column structure — overlapping, bleeding off-screen, or offset with calculated randomness.
+- **Whitespace maximization.** Aggressive use of negative space to force focus on a single element.
+- **Parallax card stacks.** Sections that stick and physically stack over each other during scroll.
+- **Split-screen scroll.** Two halves of the screen sliding in opposite directions.
+
+### Motion Upgrades
+- **Smooth scroll with inertia.** Decouple scrolling from browser defaults for a heavier, cinematic feel.
+- **Staggered entry.** Elements cascade in with slight delays, combining Y-axis translation with opacity fade. Never mount everything at once.
+- **Spring physics.** Replace linear easing with spring-based motion for a natural, weighty feel on all interactive elements.
+- **Scroll-driven reveals.** Content entering through expanding masks, wipes, or draw-on SVG paths tied to scroll progress.
+
+### Surface Upgrades
+- **True glassmorphism.** Go beyond `backdrop-filter: blur`. Add a 1px inner border and a subtle inner shadow to simulate edge refraction.
+- **Spotlight borders.** Card borders that illuminate dynamically under the cursor.
+- **Grain and noise overlays.** A fixed, pointer-events-none overlay with subtle noise to break digital flatness.
+- **Colored, tinted shadows.** Shadows that carry the hue of the background rather than using generic black.
+
+## Fix Priority
+
+Apply changes in this order for maximum visual impact with minimum risk:
+
+1. **Font swap** — biggest instant improvement, lowest risk
+2. **Color palette cleanup** — remove clashing or oversaturated colors
+3. **Hover and active states** — makes the interface feel alive
+4. **Layout and spacing** — proper grid, max-width, consistent padding
+5. **Replace generic components** — swap cliche patterns for modern alternatives
+6. **Add loading, empty, and error states** — makes it feel finished
+7. **Polish typography scale and spacing** — the premium final touch
+
+## Rules
+
+- Work with the existing tech stack. Do not migrate frameworks or styling libraries.
+- Do not break existing functionality. Test after every change.
+- Before importing any new library, check the project's dependency file first.
+- If the project uses Tailwind, check the version (v3 vs v4) before modifying config.
+- If the project has no framework, use vanilla CSS.
+- Keep changes reviewable and focused. Small, targeted improvements over big rewrites.

.agents/skills/stitch-design-taste/DESIGN.md

@@ -0,0 +1,121 @@
+# Design System: Taste Standard
+**Skill:** stitch-design-taste
+
+---
+
+## Configuration — Set Your Style
+Adjust these dials before using this design system. They control how creative, dense, and animated the output should be. Pick the level that fits your project.
+
+| Dial | Level | Description |
+|------|-------|-------------|
+| **Creativity** | `8` | `1` = Ultra-minimal, Swiss, silent, monochrome. `5` = Balanced, clean but with personality. `10` = Expressive, editorial, bold typography experiments, inline images in headlines, strong asymmetry. Default: `8` |
+| **Density** | `4` | `1` = Gallery-airy, massive whitespace. `5` = Balanced sections. `10` = Cockpit-dense, data-heavy. Default: `4` |
+| **Variance** | `8` | `1` = Predictable, symmetric grids. `5` = Subtle offsets. `10` = Artsy chaotic, no two sections alike. Default: `8` |
+| **Motion Intent** | `6` | `1` = Static, no animation noted. `5` = Subtle hover/entrance cues. `10` = Cinematic orchestration noted in every component. Default: `6` |
+
+> **How to use:** Change the numbers above to match your project's vibe. At **Creativity 1–3**, the system produces clean, quiet, Notion-like interfaces. At **Creativity 7–10**, expect inline image typography, dramatic scale contrast, and strong editorial layouts. The rest of the rules below adapt to your chosen levels.
+
+---
+
+## 1. Visual Theme & Atmosphere
+A restrained, gallery-airy interface with confident asymmetric layouts and fluid spring-physics motion. The atmosphere is clinical yet warm — like a well-lit architecture studio where every element earns its place through function. Density is balanced (Level 4), variance runs high (Level 8) to prevent symmetrical boredom, and motion is fluid but never theatrical (Level 6). The overall impression: expensive, intentional, alive.
+
+## 2. Color Palette & Roles
+- **Canvas White** (#F9FAFB) — Primary background surface. Warm-neutral, never clinical blue-white
+- **Pure Surface** (#FFFFFF) — Card and container fill. Used with whisper shadow for elevation
+- **Charcoal Ink** (#18181B) — Primary text. Zinc-950 depth — never pure black
+- **Steel Secondary** (#71717A) — Body text, descriptions, metadata. Zinc-500 warmth
+- **Muted Slate** (#94A3B8) — Tertiary text, timestamps, disabled states
+- **Whisper Border** (rgba(226,232,240,0.5)) — Card borders, structural 1px lines. Semi-transparent for depth
+- **Diffused Shadow** (rgba(0,0,0,0.05)) — Card elevation. Wide-spreading, 40px blur, -15px offset. Never harsh
+
+### Accent Selection (Pick ONE per project)
+- **Emerald Signal** (#10B981) — For growth, success, positive data dashboards
+- **Electric Blue** (#3B82F6) — For productivity, SaaS, developer tools
+- **Deep Rose** (#E11D48) — For creative, editorial, fashion-adjacent projects
+- **Amber Warmth** (#F59E0B) — For community, social, warm-toned products
+
+### Banned Colors
+- Purple/Violet neon gradients — the "AI Purple" aesthetic
+- Pure Black (#000000) — always Off-Black or Zinc-950
+- Oversaturated accents above 80% saturation
+- Mixed warm/cool gray systems within one project
+
+## 3. Typography Rules
+- **Display:** `Geist`, `Satoshi`, `Cabinet Grotesk`, or `Outfit` — Track-tight (`-0.025em`), controlled fluid scale, weight-driven hierarchy (700–900). Not screaming. Leading compressed (`1.1`). Alternatives forced — `Inter` is BANNED for premium contexts
+- **Body:** Same family at weight 400 — Relaxed leading (`1.65`), 65ch max-width, Steel Secondary color (#71717A)
+- **Mono:** `Geist Mono` or `JetBrains Mono` — For code blocks, metadata, timestamps. When density exceeds Level 7, all numbers switch to monospace
+- **Scale:** Display at `clamp(2.25rem, 5vw, 3.75rem)`. Body at `1rem/1.125rem`. Mono metadata at `0.8125rem`
+
+### Banned Fonts
+- `Inter` — banned everywhere in premium/creative contexts
+- Generic serif fonts (`Times New Roman`, `Georgia`, `Garamond`, `Palatino`) — BANNED. If serif is needed for editorial/creative, use only distinctive modern serifs like `Fraunces`, `Gambarino`, `Editorial New`, or `Instrument Serif`. Never use default browser serif stacks. Serif is always BANNED in dashboards or software UIs regardless
+
+## 4. Component Stylings
+* **Buttons:** Flat surface, no outer glow. Primary: accent fill with white text. Secondary: ghost/outline. Active state: `-1px translateY` or `scale(0.98)` for tactile push. Hover: subtle background shift, never glow
+* **Cards/Containers:** Generously rounded corners (`2.5rem`). Pure white fill. Whisper border (`1px`, semi-transparent). Diffused shadow (`0 20px 40px -15px rgba(0,0,0,0.05)`). Internal padding `2rem–2.5rem`. Used ONLY when elevation communicates hierarchy — high-density layouts replace cards with `border-top` dividers or negative space
+* **Inputs/Forms:** Label positioned above input. Helper text optional. Error text below in Deep Rose. Focus ring in accent color, `2px` offset. No floating labels. Standard `0.5rem` gap between label-input-error stack
+* **Navigation:** Sleek, sticky. Icons scale on hover (Dock Magnification optional). No hamburger on desktop. Clean horizontal with generous spacing
+* **Loaders:** Skeletal shimmer matching exact layout dimensions and rounded corners. Shifting light reflection across placeholder shapes. Never circular spinners
+* **Empty States:** Composed illustration or icon composition with guidance text. Never just "No data found"
+* **Error States:** Inline, contextual. Red accent underline or border. Clear recovery action
+
+## 5. Hero Section
+The Hero is the first impression — it must be striking, creative, and never generic.
+- **Inline Image Typography:** Embed small, contextual photos or visuals directly between words or letters in the headline. Example: "We build [photo of hands typing] digital [photo of screen] products" — images sit inline at type-height, rounded, acting as visual punctuation between words. This is the signature creative technique
+- **No Overlapping Elements:** Text must never overlap images or other text. Every element has its own clear spatial zone. No z-index stacking of content layers, no absolute-positioned headlines over images. Clean separation always
+- **No Filler Text:** "Scroll to explore", "Swipe down", scroll arrow icons, bouncing chevrons, and any instructional UI chrome are BANNED. The user knows how to scroll. Let the content pull them in naturally
+- **Asymmetric Structure:** Centered Hero layouts are BANNED at this variance level. Use Split Screen (50/50), Left-Aligned text / Right visual, or Asymmetric Whitespace with large empty zones
+- **CTA Restraint:** Maximum one primary CTA button. No secondary "Learn more" links. No redundant micro-copy below the headline
+
+## 6. Layout Principles
+- **Grid-First:** CSS Grid for all structural layouts. Never flexbox percentage math (`calc(33% - 1rem)` is BANNED)
+- **No Overlapping:** Elements must never overlap each other. No absolute-positioned layers stacking content on content. Every element occupies its own grid cell or flow position. Clean, separated spatial zones
+- **Feature Sections:** The "3 equal cards in a row" pattern is BANNED. Use 2-column Zig-Zag, asymmetric Bento grids (2fr 1fr 1fr), or horizontal scroll galleries
+- **Containment:** All content within `max-width: 1400px`, centered. Generous horizontal padding (`1rem` mobile, `2rem` tablet, `4rem` desktop)
+- **Full-Height:** Use `min-height: 100dvh` — never `height: 100vh` (iOS Safari address bar jump)
+- **Bento Architecture:** For feature grids, use Row 1: 3 columns | Row 2: 2 columns (70/30 split). Each tile contains a perpetual micro-animation
+
+## 7. Responsive Rules
+Every screen must work flawlessly across all viewports. **Responsive is not optional — it is a hard requirement. Every single element must be tested at 375px, 768px, and 1440px.**
+- **Mobile-First Collapse (< 768px):** All multi-column layouts collapse to a strict single column. `width: 100%`, `padding: 1rem`, `gap: 1.5rem`. No exceptions
+- **No Horizontal Scroll:** Horizontal overflow on mobile is a critical failure. All elements must fit within viewport width. If any element causes horizontal scroll, the design is broken
+- **Typography Scaling:** Headlines scale down gracefully via `clamp()`. Body text stays `1rem` minimum. Never shrink body below `14px`. Headlines must remain readable on 375px screens
+- **Touch Targets:** All interactive elements minimum `44px` tap target. Generous spacing between clickable items. Buttons must be full-width on mobile
+- **Image Behavior:** Hero and inline images scale proportionally. Inline typography images (photos between words) stack below the headline on mobile instead of inline
+- **Navigation:** Desktop horizontal nav collapses to a clean mobile menu (slide-in or full-screen overlay). No tiny hamburger icons without labels
+- **Cards & Grids:** Bento grids and asymmetric layouts revert to stacked single-column cards with full-width. Maintain internal padding (`1rem`)
+- **Spacing Consistency:** Vertical section gaps reduce proportionally on mobile (`clamp(3rem, 8vw, 6rem)`). Never cramped, never excessively airy
+- **Testing Viewports:** Designs must be verified at: `375px` (iPhone SE), `390px` (iPhone 14), `768px` (iPad), `1024px` (small laptop), `1440px` (desktop)
+
+## 8. Motion & Interaction (Code-Phase Intent)
+> **Note:** Stitch generates static screens — it does not animate. This section documents the **intended motion behavior** so that the coding agent (Antigravity, Cursor, etc.) knows exactly how to implement animations when building the exported design into a live product.
+
+- **Physics Engine:** Spring-based exclusively. `stiffness: 100, damping: 20`. No linear easing anywhere. Premium, weighty feel on all interactive elements
+- **Perpetual Micro-Loops:** Every active dashboard component has an infinite-loop state — Pulse on status dots, Typewriter on search bars, Float on feature icons, Shimmer on loading states
+- **Staggered Orchestration:** Lists and grids mount with cascaded delays (`animation-delay: calc(var(--index) * 100ms)`). Waterfall reveals, never instant mount
+- **Layout Transitions:** Smooth re-ordering via shared element IDs. Items swap positions with physics, simulating real-time intelligence
+- **Hardware Rules:** Animate ONLY `transform` and `opacity`. Never `top`, `left`, `width`, `height`. Grain/noise filters on fixed, pointer-events-none pseudo-elements only
+- **Performance:** CPU-heavy perpetual animations isolated in microscopic leaf components. Never trigger parent re-renders. Target 60fps minimum
+
+## 9. Anti-Patterns (Banned)
+- No emojis — anywhere in UI, code, or alt text
+- No `Inter` font — use `Geist`, `Outfit`, `Cabinet Grotesk`, `Satoshi`
+- No generic serif fonts (`Times New Roman`, `Georgia`, `Garamond`) — if serif is needed, use distinctive modern serifs only (`Fraunces`, `Instrument Serif`)
+- No pure black (`#000000`) — Off-Black or Zinc-950 only
+- No neon outer glows or default box-shadow glows
+- No oversaturated accent colors above 80%
+- No excessive gradient text on large headers
+- No custom mouse cursors
+- No overlapping elements — text never overlaps images or other content. Clean spatial separation always
+- No 3-column equal card layouts for features
+- No centered Hero sections (at this variance level)
+- No filler UI text: "Scroll to explore", "Swipe down", "Discover more below", scroll arrows, bouncing chevrons — all BANNED
+- No generic names: "John Doe", "Sarah Chan", "Acme", "Nexus", "SmartFlow"
+- No fake round numbers: `99.99%`, `50%`, `1234567` — use organic data: `47.2%`, `+1 (312) 847-1928`
+- No AI copywriting clichés: "Elevate", "Seamless", "Unleash", "Next-Gen", "Revolutionize"
+- No broken Unsplash links — use `picsum.photos/seed/{id}/800/600` or SVG UI Avatars
+- No generic `shadcn/ui` defaults — customize radii, colors, shadows to match this system
+- No `z-index` spam — use only for Navbar, Modal, Overlay layer contexts
+- No `h-screen` — always `min-h-[100dvh]`
+- No circular loading spinners — skeletal shimmer only

.agents/skills/stitch-design-taste/SKILL.md

@@ -0,0 +1,184 @@
+---
+name: stitch-design-taste
+description: Semantic Design System Skill for Google Stitch. Generates agent-friendly DESIGN.md files that enforce premium, anti-generic UI standards — strict typography, calibrated color, asymmetric layouts, perpetual micro-motion, and hardware-accelerated performance.
+---
+
+# Stitch Design Taste — Semantic Design System Skill
+
+## Overview
+This skill generates `DESIGN.md` files optimized for Google Stitch screen generation. It translates the battle-tested anti-slop frontend engineering directives into Stitch's native semantic design language — descriptive, natural-language rules paired with precise values that Stitch's AI agent can interpret to produce premium, non-generic interfaces.
+
+The generated `DESIGN.md` serves as the **single source of truth** for prompting Stitch to generate new screens that align with a curated, high-agency design language. Stitch interprets design through **"Visual Descriptions"** supported by specific color values, typography specs, and component behaviors.
+
+## Prerequisites
+- Access to Google Stitch via [labs.google/stitch](https://labs.google/stitch)
+- Optionally: Stitch MCP Server for programmatic integration with Cursor, Antigravity, or Gemini CLI
+
+## The Goal
+Generate a `DESIGN.md` file that encodes:
+1. **Visual atmosphere** — the mood, density, and design philosophy
+2. **Color calibration** — neutrals, accents, and banned patterns with hex codes
+3. **Typographic architecture** — font stacks, scale hierarchy, and anti-patterns
+4. **Component behaviors** — buttons, cards, inputs with interaction states
+5. **Layout principles** — grid systems, spacing philosophy, responsive strategy
+6. **Motion philosophy** — animation engine specs, spring physics, perpetual micro-interactions
+7. **Anti-patterns** — explicit list of banned AI design clichés
+
+## Analysis & Synthesis Instructions
+
+### 1. Define the Atmosphere
+Evaluate the target project's intent. Use evocative adjectives from the taste spectrum:
+- **Density:** "Art Gallery Airy" (1–3) → "Daily App Balanced" (4–7) → "Cockpit Dense" (8–10)
+- **Variance:** "Predictable Symmetric" (1–3) → "Offset Asymmetric" (4–7) → "Artsy Chaotic" (8–10)
+- **Motion:** "Static Restrained" (1–3) → "Fluid CSS" (4–7) → "Cinematic Choreography" (8–10)
+
+Default baseline: Variance 8, Motion 6, Density 4. Adapt dynamically based on user's vibe description.
+
+### 2. Map the Color Palette
+For each color provide: **Descriptive Name** + **Hex Code** + **Functional Role**.
+
+**Mandatory constraints:**
+- Maximum 1 accent color. Saturation below 80%
+- The "AI Purple/Blue Neon" aesthetic is strictly BANNED — no purple button glows, no neon gradients
+- Use absolute neutral bases (Zinc/Slate) with high-contrast singular accents
+- Stick to one palette for the entire output — no warm/cool gray fluctuation
+- Never use pure black (`#000000`) — use Off-Black, Zinc-950, or Charcoal
+
+### 3. Establish Typography Rules
+- **Display/Headlines:** Track-tight, controlled scale. Not screaming. Hierarchy through weight and color, not just massive size
+- **Body:** Relaxed leading, max 65 characters per line
+- **Font Selection:** `Inter` is BANNED for premium/creative contexts. Force unique character: `Geist`, `Outfit`, `Cabinet Grotesk`, or `Satoshi`
+- **Serif Ban:** Generic serif fonts (`Times New Roman`, `Georgia`, `Garamond`, `Palatino`) are BANNED. If serif is needed for editorial/creative contexts, use only distinctive modern serifs: `Fraunces`, `Gambarino`, `Editorial New`, or `Instrument Serif`. Serif is always BANNED in dashboards or software UIs
+- **Dashboard Constraint:** Use Sans-Serif pairings exclusively (`Geist` + `Geist Mono` or `Satoshi` + `JetBrains Mono`)
+- **High-Density Override:** When density exceeds 7, all numbers must use Monospace
+
+### 4. Define the Hero Section
+The Hero is the first impression and must be creative, striking, and never generic:
+- **Inline Image Typography:** Embed small, contextual photos or visuals directly between words or letters in the headline. Images sit inline at type-height, rounded, acting as visual punctuation. This is the signature creative technique
+- **No Overlapping:** Text must never overlap images or other text. Every element occupies its own clean spatial zone
+- **No Filler Text:** "Scroll to explore", "Swipe down", scroll arrow icons, bouncing chevrons are BANNED. The content should pull users in naturally
+- **Asymmetric Structure:** Centered Hero layouts BANNED when variance exceeds 4
+- **CTA Restraint:** Maximum one primary CTA. No secondary "Learn more" links
+
+### 5. Describe Component Stylings
+For each component type, describe shape, color, shadow depth, and interaction behavior:
+- **Buttons:** Tactile push feedback on active state. No neon outer glows. No custom mouse cursors
+- **Cards:** Use ONLY when elevation communicates hierarchy. Tint shadows to background hue. For high-density layouts, replace cards with border-top dividers or negative space
+- **Inputs/Forms:** Label above input, helper text optional, error text below. Standard gap spacing
+- **Loading States:** Skeletal loaders matching layout dimensions — no generic circular spinners
+- **Empty States:** Composed compositions indicating how to populate data
+- **Error States:** Clear, inline error reporting
+
+### 6. Define Layout Principles
+- No overlapping elements — every element occupies its own clear spatial zone. No absolute-positioned content stacking
+- Centered Hero sections are BANNED when variance exceeds 4 — force Split Screen, Left-Aligned, or Asymmetric Whitespace
+- The generic "3 equal cards horizontally" feature row is BANNED — use 2-column Zig-Zag, asymmetric grid, or horizontal scroll
+- CSS Grid over Flexbox math — never use `calc()` percentage hacks
+- Contain layouts using max-width constraints (e.g., 1400px centered)
+- Full-height sections must use `min-h-[100dvh]` — never `h-screen` (iOS Safari catastrophic jump)
+
+### 7. Define Responsive Rules
+Every design must work across all viewports:
+- **Mobile-First Collapse (< 768px):** All multi-column layouts collapse to single column. No exceptions
+- **No Horizontal Scroll:** Horizontal overflow on mobile is a critical failure
+- **Typography Scaling:** Headlines scale via `clamp()`. Body text minimum `1rem`/`14px`
+- **Touch Targets:** All interactive elements minimum `44px` tap target
+- **Image Behavior:** Inline typography images (photos between words) stack below headline on mobile
+- **Navigation:** Desktop horizontal nav collapses to clean mobile menu
+- **Spacing:** Vertical section gaps reduce proportionally (`clamp(3rem, 8vw, 6rem)`)
+
+### 8. Encode Motion Philosophy
+- **Spring Physics default:** `stiffness: 100, damping: 20` — premium, weighty feel. No linear easing
+- **Perpetual Micro-Interactions:** Every active component should have an infinite loop state (Pulse, Typewriter, Float, Shimmer)
+- **Staggered Orchestration:** Never mount lists instantly — use cascade delays for waterfall reveals
+- **Performance:** Animate exclusively via `transform` and `opacity`. Never animate `top`, `left`, `width`, `height`. Grain/noise filters on fixed pseudo-elements only
+
+### 9. List Anti-Patterns (AI Tells)
+Encode these as explicit "NEVER DO" rules in the DESIGN.md:
+- No emojis anywhere
+- No `Inter` font
+- No generic serif fonts (`Times New Roman`, `Georgia`, `Garamond`) — distinctive modern serifs only if needed
+- No pure black (`#000000`)
+- No neon/outer glow shadows
+- No oversaturated accents
+- No excessive gradient text on large headers
+- No custom mouse cursors
+- No overlapping elements — clean spatial separation always
+- No 3-column equal card layouts
+- No generic names ("John Doe", "Acme", "Nexus")
+- No fake round numbers (`99.99%`, `50%`)
+- No AI copywriting clichés ("Elevate", "Seamless", "Unleash", "Next-Gen")
+- No filler UI text: "Scroll to explore", "Swipe down", scroll arrows, bouncing chevrons
+- No broken Unsplash links — use `picsum.photos` or SVG avatars
+- No centered Hero sections (for high-variance projects)
+
+## Output Format (DESIGN.md Structure)
+
+```markdown
+# Design System: [Project Title]
+
+## 1. Visual Theme & Atmosphere
+(Evocative description of the mood, density, variance, and motion intensity.
+Example: "A restrained, gallery-airy interface with confident asymmetric layouts
+and fluid spring-physics motion. The atmosphere is clinical yet warm — like a
+well-lit architecture studio.")
+
+## 2. Color Palette & Roles
+- **Canvas White** (#F9FAFB) — Primary background surface
+- **Pure Surface** (#FFFFFF) — Card and container fill
+- **Charcoal Ink** (#18181B) — Primary text, Zinc-950 depth
+- **Muted Steel** (#71717A) — Secondary text, descriptions, metadata
+- **Whisper Border** (rgba(226,232,240,0.5)) — Card borders, 1px structural lines
+- **[Accent Name]** (#XXXXXX) — Single accent for CTAs, active states, focus rings
+(Max 1 accent. Saturation < 80%. No purple/neon.)
+
+## 3. Typography Rules
+- **Display:** [Font Name] — Track-tight, controlled scale, weight-driven hierarchy
+- **Body:** [Font Name] — Relaxed leading, 65ch max-width, neutral secondary color
+- **Mono:** [Font Name] — For code, metadata, timestamps, high-density numbers
+- **Banned:** Inter, generic system fonts for premium contexts. Serif fonts banned in dashboards.
+
+## 4. Component Stylings
+* **Buttons:** Flat, no outer glow. Tactile -1px translate on active. Accent fill for primary, ghost/outline for secondary.
+* **Cards:** Generously rounded corners (2.5rem). Diffused whisper shadow. Used only when elevation serves hierarchy. High-density: replace with border-top dividers.
+* **Inputs:** Label above, error below. Focus ring in accent color. No floating labels.
+* **Loaders:** Skeletal shimmer matching exact layout dimensions. No circular spinners.
+* **Empty States:** Composed, illustrated compositions — not just "No data" text.
+
+## 5. Layout Principles
+(Grid-first responsive architecture. Asymmetric splits for Hero sections.
+Strict single-column collapse below 768px. Max-width containment.
+No flexbox percentage math. Generous internal padding.)
+
+## 6. Motion & Interaction
+(Spring physics for all interactive elements. Staggered cascade reveals.
+Perpetual micro-loops on active dashboard components. Hardware-accelerated
+transforms only. Isolated Client Components for CPU-heavy animations.)
+
+## 7. Anti-Patterns (Banned)
+(Explicit list of forbidden patterns: no emojis, no Inter, no pure black,
+no neon glows, no 3-column equal grids, no AI copywriting clichés,
+no generic placeholder names, no broken image links.)
+```
+
+## Best Practices
+- **Be Descriptive:** "Deep Charcoal Ink (#18181B)" — not just "dark text"
+- **Be Functional:** Explain what each element is used for
+- **Be Consistent:** Same terminology throughout the document
+- **Be Precise:** Include exact hex codes, rem values, pixel values in parentheses
+- **Be Opinionated:** This is not a neutral template — it enforces a specific, premium aesthetic
+
+## Tips for Success
+1. Start with the atmosphere — understand the vibe before detailing tokens
+2. Look for patterns — identify consistent spacing, sizing, and styling
+3. Think semantically — name colors by purpose, not just appearance
+4. Consider hierarchy — document how visual weight communicates importance
+5. Encode the bans — anti-patterns are as important as the rules themselves
+
+## Common Pitfalls to Avoid
+- Using technical jargon without translation ("rounded-xl" instead of "generously rounded corners")
+- Omitting hex codes or using only descriptive names
+- Forgetting functional roles of design elements
+- Being too vague in atmosphere descriptions
+- Ignoring the anti-pattern list — these are what make the output premium
+- Defaulting to generic "safe" designs instead of enforcing the curated aesthetic

.claude/skills/brandkit/SKILL.md

@@ -0,0 +1,798 @@
+---
+name: brandkit
+description: Premium brand-kit image generation skill for creating high-end brand-guidelines boards, logo systems, identity decks, and visual-world presentations. Trained for minimalist, cinematic, editorial, dark-tech, luxury, cultural, security, gaming, developer-tool, and consumer-app brand systems. Optimized for intentional logo concepting, refined composition, sparse typography, strong symbolic meaning, premium mockups, art-directed imagery, and flexible grid layouts.
+---
+
+# BRANDKIT IMAGE GENERATION SKILL
+
+You are an elite brand identity art director, logo designer, visual-system strategist, and presentation designer.
+
+Your job is to generate premium brand-kit images that feel like they came from a serious identity studio.
+
+The output must feel:
+- intentional
+- premium
+- minimal
+- coherent
+- strategic
+- visually expensive
+- brand-system driven
+- presentation-ready
+
+Do not generate generic logos.  
+Do not generate random mockups.  
+Do not generate messy AI moodboards.
+
+Create a complete brand world in one image.
+
+---
+
+# REFERENCE STYLE DNA
+
+The desired visual quality is inspired by premium brand-guidelines decks with:
+
+- dark charcoal outer canvas
+- clean grid-based presentation boards
+- strong gutters between panels
+- restrained visual density
+- very sparse typography
+- large negative space
+- cinematic brand atmosphere
+- simple but memorable logo marks
+- UI mockups used as brand applications
+- browser chrome / app headers / terminal frames
+- image-led panels with subtle overlays
+- halftone, grain, scanline, or print texture
+- geometric construction diagrams
+- small labels and page-number details
+- muted but powerful accent colors
+- logo repeated across multiple touchpoints
+- one strong brand idea per board
+
+The references are not a fixed style.  
+They define the quality bar, restraint, and presentation logic.
+
+---
+
+# CORE PRINCIPLE
+
+A premium brand kit is not decoration.
+
+It is a visual argument for why the brand exists.
+
+Every generated board must answer:
+
+1. What does this brand represent?
+2. What is the core metaphor?
+3. How does the logo express that?
+4. How does the system scale across UI, print, image, and detail?
+5. Why does the whole thing feel ownable?
+
+---
+
+# DEFAULT OUTPUT
+
+Unless the user specifies otherwise:
+
+- Generate one brand-kit overview image
+- Default layout: `3 × 3`
+- Default aspect ratio: `4:3` or `16:10`
+- Use a clean presentation grid
+- Use consistent gutters
+- Use minimal text
+- Make every panel feel connected
+
+Allowed layouts:
+- `3 × 3` full identity system
+- `2 × 3` cinematic brand deck overview
+- `2 × 2` compact concept board
+- `1 × 3` horizontal brand strip
+- `4 × 2` wide contact-sheet layout
+- custom layout when requested
+
+If the user gives references, match their quality and rhythm, not their exact content.
+
+---
+
+# BRAND STRATEGY FIRST
+
+Before generating, infer the brand strategy.
+
+Think through:
+
+- category
+- audience
+- product function
+- emotional promise
+- cultural position
+- trust level
+- visual world
+- symbolic metaphor
+- what the brand should avoid
+
+The visual system must be based on meaning.
+
+Examples:
+
+| Category | Core Ideas | Possible Symbol Logic |
+|---|---|---|
+| Developer tool | building, speed, precision, control | cursor, frame, bolt, scaffold, grid |
+| AI assistant | delegation, intelligence, clarity | spark, orbit, signal, path, node |
+| Security | protection, vigilance, boundary | shield, eye, seal, protected core |
+| Gaming / betting | chance, reward, tension, speed | dice, gem, card, signal, trophy |
+| Voice AI | sound, rhythm, command, flow | waveform, mic, orb, speech path |
+| Compliance | trust, order, rules, protection | seal, dog, badge, document, shield |
+| Drone / robotics | flight, control, vision, mission | wing, owl, crosshair, path, zone |
+| Luxury / editorial | taste, material, ritual, restraint | monogram, seal, paper, emboss, mark |
+| Productivity | focus, momentum, clarity | path, check, block, calendar, light |
+
+Do not pick symbols randomly.
+
+---
+
+# LOGO GENERATION STANDARD
+
+The logo must be professional.
+
+It should be:
+- simple
+- memorable
+- symbolic
+- scalable
+- ownable
+- visually balanced
+- connected to the brand idea
+- usable as icon, wordmark, badge, UI mark, and pattern
+
+Avoid:
+- generic lightning bolts unless strongly justified
+- random animals
+- fake luxury crests
+- copied famous marks
+- overcomplicated symbols
+- clipart-style icons
+- meaningless sparkles
+- inconsistent logo variants
+
+The logo should feel like it came from research and reduction.
+
+---
+
+# LOGO CONCEPT METHODS
+
+Use one or combine two maximum.
+
+## 1. Monogram + Meaning
+
+Combine the brand initial with a metaphor.
+
+Examples:
+- `K` + kite / frame / direction
+- `N` + path / folded system
+- `S` + sound wave / speech flow
+- `A` + ascent / architecture / momentum
+
+Do not make a boring letter icon.  
+Use negative space, cuts, folds, or geometry.
+
+---
+
+## 2. Product Action
+
+Turn the product's main action into a symbol.
+
+Examples:
+- build → frame, scaffold, block, cursor
+- protect → shield, boundary, watch mark
+- convert → switch, arrow, transformation shape
+- speak → waveform, mic, pulse
+- hunt threats → eye, raptor, radar, trace
+- automate → loop, handoff, path
+
+Make it abstract and premium, not literal.
+
+---
+
+## 3. Metaphor Fusion
+
+Combine two meaningful ideas into one reduced mark.
+
+Examples:
+- owl + drone vision
+- shield + mountain
+- moon + waveform
+- dog + compliance seal
+- dice + mobile game economy
+- cursor + lightning speed
+- kite + product frame
+
+The fusion should be subtle and readable.
+
+---
+
+## 4. Negative Space
+
+Use empty space to create intelligence.
+
+Examples:
+- hidden arrow
+- protected center
+- cutout initial
+- internal path
+- folded corner
+- eye formed by crossing shapes
+
+Negative space should be crisp.
+
+---
+
+## 5. Construction Geometry
+
+Create a mark from a clear system.
+
+Use:
+- circles
+- diagonal cuts
+- grids
+- frames
+- modular blocks
+- layered cards
+- orbital paths
+- crosshairs
+- measured linework
+
+One panel can show construction logic.
+
+---
+
+# BOARD COMPOSITION DNA
+
+A strong brand-kit board should feel like a curated sequence.
+
+Use:
+- large calm cover panel
+- one digital mockup panel
+- one image-led atmosphere panel
+- one system/construction panel
+- one physical or icon application panel
+- one quiet tagline panel
+
+Do not make every panel equally loud.
+
+The board should have rhythm:
+- quiet
+- functional
+- emotional
+- technical
+- atmospheric
+- detailed
+
+---
+
+# DEFAULT 3 × 3 PANEL SYSTEM
+
+Use this if no layout is specified:
+
+## 1. Logo Cover
+Large logo and wordmark.  
+Minimal title.  
+Strong negative space.
+
+## 2. Logo Construction
+Symbol breakdown, grid, geometry, or negative-space logic.  
+Show why the mark exists.
+
+## 3. Digital Application
+Browser chrome, app header, terminal, dashboard fragment, or app icon.
+
+## 4. Brand Essence
+One short tagline.  
+Large readable typography.  
+Sparse composition.
+
+## 5. Color System
+Swatches, gradient strips, color discs, material chips, or palette cards.
+
+## 6. Typography
+Large type specimen, alphabet row, or primary/secondary type pairing.
+
+## 7. Physical Application
+Card, folder, badge, poster, label, seal, packaging, or object mockup.
+
+## 8. Image Direction
+Cinematic landscape, product crop, halftone poster, editorial scene, material texture.
+
+## 9. System Detail
+UI chips, input bar, command line, icon row, badge system, component strip, pattern detail.
+
+---
+
+# 2 × 3 REFERENCE-STYLE LAYOUT
+
+For boards like the uploaded references, use:
+
+1. **Logo / Wordmark**
+   - centered or offset
+   - extremely minimal
+
+2. **Browser / Product Surface**
+   - browser bar, app frame, prompt input, or URL field
+
+3. **Command / Functional Panel**
+   - terminal, prompt bar, input state, install command, dashboard fragment
+
+4. **Atmosphere / Campaign Image**
+   - halftone landscape, cinematic image, product-world visual, or art-directed photo
+
+5. **Symbol / Construction / Badge**
+   - logo mark in target, seal, geometric frame, icon construction
+
+6. **Tagline / System Promise**
+   - one short line
+   - large type
+   - quiet background
+
+This layout should feel like a premium mini-deck.
+
+---
+
+# VISUAL MODES
+
+Choose based on the brand.
+
+## Dark Developer / Builder
+
+Use for:
+developer tools, coding agents, infra, automation, AI builders.
+
+Visual cues:
+- near-black panels
+- monospace accents
+- command lines
+- terminal windows
+- prompt bars
+- subtle grid
+- cyan, blue, coral, or lime accents
+- pixel or CRT texture if appropriate
+
+Logo logic:
+- cursor + frame
+- bolt + build speed
+- scaffold + monogram
+- terminal glyph + symbol
+- modular construction mark
+
+Mood:
+precise, sharp, confident, builder-native.
+
+---
+
+## Dark Product / Operator
+
+Use for:
+business tools, growth tools, sales agents, automation, productivity.
+
+Visual cues:
+- black / dark red / amber
+- glowing UI chips
+- card systems
+- segmented flows
+- icon rows
+- reward/progress motifs
+- minimal hero text
+
+Logo logic:
+- signal, gift, path, operator mark, switch, loop, command system
+
+Mood:
+fast, operational, tactical, premium.
+
+---
+
+## Dark Nature / Calm System
+
+Use for:
+strategy, travel, wellness, climate, quiet premium SaaS.
+
+Visual cues:
+- deep green
+- lime accent
+- misty landscapes
+- image UI circles
+- soft overlays
+- calm page labels
+- dark editorial grid
+
+Logo logic:
+- path, leaf, moon, horizon, compass, portal, folded mark
+
+Mood:
+calm, trustworthy, focused.
+
+---
+
+## Dark Security / Threat Intelligence
+
+Use for:
+security, compliance, monitoring, network products.
+
+Visual cues:
+- black/navy
+- shield forms
+- radar lines
+- threat labels
+- subtle motion traces
+- red/blue alert chips
+- controlled gradients
+
+Logo logic:
+- shield, raptor, eye, watch, boundary, protected core
+
+Mood:
+serious, vigilant, precise.
+
+---
+
+## Light Editorial / Compliance
+
+Use for:
+legal, privacy, compliance, documents, trust brands.
+
+Visual cues:
+- warm ivory
+- paper texture
+- small serif labels
+- seals / badges
+- color wheel / palette object
+- calm stationery
+- deep blue, red, gold accents
+
+Logo logic:
+- seal, dog, shield, document, stamp, monogram
+
+Mood:
+trustworthy, refined, institutional but modern.
+
+---
+
+## Luxury / Beauty / Fashion
+
+Use for:
+beauty, fashion, hospitality, premium services.
+
+Visual cues:
+- ivory / stone / espresso
+- serif wordmark
+- elegant monogram
+- paper grain
+- embossing
+- product labels
+- editorial crops
+- soft shadows
+
+Logo logic:
+- monogram, seal, petal, vessel, ritual object, refined typographic mark
+
+Mood:
+tasteful, adult, expensive.
+
+---
+
+## Voice / Communication
+
+Use for:
+voice AI, chat, assistants, speech, audio.
+
+Visual cues:
+- dark indigo
+- lilac glow
+- waveform
+- mic motif
+- phone crop
+- command input
+- app icon
+
+Logo logic:
+- wave + initial
+- sound orb
+- speech path
+- microphone abstraction
+- pulse ring
+
+Mood:
+fluid, intelligent, intimate.
+
+---
+
+## Cultural / Experimental
+
+Use for:
+music, creative tools, events, gaming-adjacent, cultural products.
+
+Visual cues:
+- halftone
+- CRT texture
+- analog print
+- bold accent color
+- poster-style panels
+- unexpected image crops
+- simple but punchy logo
+
+Logo logic:
+- custom wordmark
+- icon with attitude
+- symbolic mascot
+- print-inspired mark
+
+Mood:
+memorable, creative, still controlled.
+
+---
+
+# PREMIUM DETAIL LANGUAGE
+
+Use details like:
+- small page numbers
+- tiny footer labels
+- precise alignment marks
+- construction lines
+- subtle crosshair grids
+- thin rules
+- browser bars
+- rounded rectangles
+- image masks
+- soft shadows
+- low-opacity texture
+- halftone image treatment
+- one highlighted word
+- one accent chip
+- one strong icon state
+
+Do not overuse them.
+
+Premium detail should reward looking closer.
+
+---
+
+# TEXT RULES
+
+Use very little text.
+
+Good text:
+- brand name
+- one tagline
+- one URL
+- one command
+- 2–5 section labels
+- short UI chips
+
+Bad text:
+- long paragraphs
+- tiny fake body copy
+- lots of menu items
+- lorem ipsum
+- dense explanations
+- unreadable labels
+
+Text should be large enough and sparse enough to render well.
+
+---
+
+# TAGLINE STYLE
+
+Taglines should be short and specific.
+
+Good:
+- "What will you build today?"
+- "Nothing random."
+- "Your network. Our watch."
+- "Build better."
+- "On guard."
+- "Every mission under control."
+- "Everything operators need."
+- "Clarity builds confidence."
+
+Avoid:
+- generic corporate slogans
+- long marketing copy
+- buzzword soup
+- fake inspirational fluff
+
+---
+
+# IMAGE DIRECTION
+
+Images should feel art-directed.
+
+Use:
+- cinematic mountains
+- dusk skies
+- landscapes with brand overlays
+- halftone clouds
+- CRT screen scenes
+- dark product closeups
+- dramatic object crops
+- textured paper backgrounds
+- moody architecture
+- abstract but controlled visual systems
+
+Avoid:
+- generic stock people
+- random office photos
+- cliché robot imagery
+- overbusy scenes
+- unrelated imagery
+
+Images should match the palette and metaphor.
+
+---
+
+# MOCKUP DIRECTION
+
+Mockups should be minimal and believable.
+
+Use:
+- browser chrome
+- URL bar
+- terminal window
+- command prompt
+- app icon
+- phone corner crop
+- card stack
+- badge
+- seal
+- folder
+- UI chips
+- dashboard fragment
+- input bar
+- product label
+
+Avoid:
+- full fake dashboards with too much data
+- cheap glossy mockups
+- random device overload
+- busy app screens
+- excessive icons
+
+Mockups are identity applications, not feature demos.
+
+---
+
+# COLOR DISCIPLINE
+
+Use one dominant palette.
+
+Default:
+- base color
+- primary accent
+- secondary accent
+- neutrals
+
+Good reference-style palettes:
+- black + cyan + muted coral
+- black + red + cream + blue
+- forest green + lime + fog gray
+- navy + white + steel
+- ivory + deep blue + red + gold
+- black + lilac + soft purple
+- black + amber + red
+- charcoal + white + pale blue
+
+Rules:
+- accents must repeat across panels
+- no random rainbow unless requested
+- no generic purple-blue AI glow unless appropriate
+- one accent can carry the entire system
+
+---
+
+# ANTI-GENERIC RULES
+
+Never make:
+- random floating icons
+- generic startup gradients
+- overdesigned logos
+- meaningless blobs
+- messy layout collages
+- fake tiny UI
+- inconsistent logo marks
+- too many colors
+- cheap neon
+- stock-template brand boards
+- corporate PowerPoint slides
+- soulless SaaS dashboards
+
+Make the design quieter, sharper, and more intentional.
+
+---
+
+# REFERENCE USAGE
+
+When the user provides references:
+
+Extract:
+- layout rhythm
+- grid style
+- spacing
+- typography scale
+- visual density
+- logo placement
+- amount of text
+- image treatment
+- accent color logic
+- brand-system behavior
+
+Do not copy:
+- exact logo
+- exact brand name
+- exact composition
+- exact slogan
+- unique visual asset
+
+Use references as quality training, not as templates.
+
+---
+
+# PROMPT TEMPLATE
+
+Use this structure internally:
+
+Create a premium brand-kit overview image for "[BRAND NAME]".
+
+Brand strategy:
+- category: [category]
+- audience: [audience]
+- personality: [traits]
+- core metaphor: [metaphor]
+- logo idea: [how the mark combines symbol + name + category meaning]
+
+Layout:
+[3×3 / 2×3 / custom] grid on a dark or light presentation canvas with strong gutters, clean alignment, and refined negative space.
+
+Panels:
+- logo cover
+- logo concept / construction
+- digital application
+- tagline / brand essence
+- color system
+- typography
+- physical application
+- image direction
+- system detail
+
+Visual mode:
+[mode]
+
+Palette:
+[disciplined palette]
+
+Style:
+premium, sparse, cinematic, intentional, polished, brand-guidelines deck, no clutter, no copied real-world logos.
+
+Typography:
+readable, minimal, high hierarchy, no tiny fake text.
+
+Logo:
+professional, symbolic, simple, ownable, based on the brand's purpose, repeated consistently across panels.
+
+---
+
+# FINAL OUTPUT STANDARD
+
+The image must look like:
+- a premium identity deck
+- a senior designer's presentation board
+- a brand-system case study
+- a visual launch direction
+- a professional logo concept board
+
+The final result should be:
+- clean
+- strategic
+- symbolic
+- minimal
+- coherent
+- premium
+- art-directed
+- implementation-friendly
+- stronger than normal AI-generated brand visuals

.claude/skills/design-taste-frontend-v1/SKILL.md

@@ -0,0 +1,226 @@
+---
+name: design-taste-frontend-v1
+description: The original v1 taste-skill, preserved for projects depending on its exact behavior. The current default is `design-taste-frontend` (v2 experimental), which is a substantial rewrite. Use this v1 install name only if you need exact backward compatibility.
+---
+
+# High-Agency Frontend Skill
+
+## 1. ACTIVE BASELINE CONFIGURATION
+* DESIGN_VARIANCE: 8 (1=Perfect Symmetry, 10=Artsy Chaos)
+* MOTION_INTENSITY: 6 (1=Static/No movement, 10=Cinematic/Magic Physics)
+* VISUAL_DENSITY: 4 (1=Art Gallery/Airy, 10=Pilot Cockpit/Packed Data)
+
+**AI Instruction:** The standard baseline for all generations is strictly set to these values (8, 6, 4). Do not ask the user to edit this file. Otherwise, ALWAYS listen to the user: adapt these values dynamically based on what they explicitly request in their chat prompts. Use these baseline (or user-overridden) values as your global variables to drive the specific logic in Sections 3 through 7.
+
+## 2. DEFAULT ARCHITECTURE & CONVENTIONS
+Unless the user explicitly specifies a different stack, adhere to these structural constraints to maintain consistency:
+
+* **DEPENDENCY VERIFICATION [MANDATORY]:** Before importing ANY 3rd party library (e.g. `framer-motion`, `lucide-react`, `zustand`), you MUST check `package.json`. If the package is missing, you MUST output the installation command (e.g. `npm install package-name`) before providing the code. **Never** assume a library exists.
+* **Framework & Interactivity:** React or Next.js. Default to Server Components (`RSC`). 
+    * **RSC SAFETY:** Global state works ONLY in Client Components. In Next.js, wrap providers in a `"use client"` component.
+    * **INTERACTIVITY ISOLATION:** If Sections 4 or 7 (Motion/Liquid Glass) are active, the specific interactive UI component MUST be extracted as an isolated leaf component with `'use client'` at the very top. Server Components must exclusively render static layouts.
+* **State Management:** Use local `useState`/`useReducer` for isolated UI. Use global state strictly for deep prop-drilling avoidance.
+* **Styling Policy:** Use Tailwind CSS (v3/v4) for 90% of styling. 
+    * **TAILWIND VERSION LOCK:** Check `package.json` first. Do not use v4 syntax in v3 projects. 
+    * **T4 CONFIG GUARD:** For v4, do NOT use `tailwindcss` plugin in `postcss.config.js`. Use `@tailwindcss/postcss` or the Vite plugin.
+* **ANTI-EMOJI POLICY [CRITICAL]:** NEVER use emojis in code, markup, text content, or alt text. Replace symbols with high-quality icons (Radix, Phosphor) or clean SVG primitives. Emojis are BANNED.
+* **Responsiveness & Spacing:**
+  * Standardize breakpoints (`sm`, `md`, `lg`, `xl`).
+  * Contain page layouts using `max-w-[1400px] mx-auto` or `max-w-7xl`.
+  * **Viewport Stability [CRITICAL]:** NEVER use `h-screen` for full-height Hero sections. ALWAYS use `min-h-[100dvh]` to prevent catastrophic layout jumping on mobile browsers (iOS Safari).
+  * **Grid over Flex-Math:** NEVER use complex flexbox percentage math (`w-[calc(33%-1rem)]`). ALWAYS use CSS Grid (`grid grid-cols-1 md:grid-cols-3 gap-6`) for reliable structures.
+* **Icons:** You MUST use exactly `@phosphor-icons/react` or `@radix-ui/react-icons` as the import paths (check installed version). Standardize `strokeWidth` globally (e.g., exclusively use `1.5` or `2.0`).
+
+
+## 3. DESIGN ENGINEERING DIRECTIVES (Bias Correction)
+LLMs have statistical biases toward specific UI cliché patterns. Proactively construct premium interfaces using these engineered rules:
+
+**Rule 1: Deterministic Typography**
+* **Display/Headlines:** Default to `text-4xl md:text-6xl tracking-tighter leading-none`.
+    * **ANTI-SLOP:** Discourage `Inter` for "Premium" or "Creative" vibes. Force unique character using `Geist`, `Outfit`, `Cabinet Grotesk`, or `Satoshi`.
+    * **TECHNICAL UI RULE:** Serif fonts are strictly BANNED for Dashboard/Software UIs. For these contexts, use exclusively high-end Sans-Serif pairings (`Geist` + `Geist Mono` or `Satoshi` + `JetBrains Mono`).
+* **Body/Paragraphs:** Default to `text-base text-gray-600 leading-relaxed max-w-[65ch]`.
+
+**Rule 2: Color Calibration**
+* **Constraint:** Max 1 Accent Color. Saturation < 80%.
+* **THE LILA BAN:** The "AI Purple/Blue" aesthetic is strictly BANNED. No purple button glows, no neon gradients. Use absolute neutral bases (Zinc/Slate) with high-contrast, singular accents (e.g. Emerald, Electric Blue, or Deep Rose).
+* **COLOR CONSISTENCY:** Stick to one palette for the entire output. Do not fluctuate between warm and cool grays within the same project.
+
+**Rule 3: Layout Diversification**
+* **ANTI-CENTER BIAS:** Centered Hero/H1 sections are strictly BANNED when `DESIGN_VARIANCE > 4`. Force "Split Screen" (50/50), "Left Aligned content/Right Aligned asset", or "Asymmetric White-space" structures.
+
+**Rule 4: Materiality, Shadows, and "Anti-Card Overuse"**
+* **DASHBOARD HARDENING:** For `VISUAL_DENSITY > 7`, generic card containers are strictly BANNED. Use logic-grouping via `border-t`, `divide-y`, or purely negative space. Data metrics should breathe without being boxed in unless elevation (z-index) is functionally required.
+* **Execution:** Use cards ONLY when elevation communicates hierarchy. When a shadow is used, tint it to the background hue.
+
+**Rule 5: Interactive UI States**
+* **Mandatory Generation:** LLMs naturally generate "static" successful states. You MUST implement full interaction cycles:
+  * **Loading:** Skeletal loaders matching layout sizes (avoid generic circular spinners).
+  * **Empty States:** Beautifully composed empty states indicating how to populate data.
+  * **Error States:** Clear, inline error reporting (e.g., forms).
+  * **Tactile Feedback:** On `:active`, use `-translate-y-[1px]` or `scale-[0.98]` to simulate a physical push indicating success/action.
+
+**Rule 6: Data & Form Patterns**
+* **Forms:** Label MUST sit above input. Helper text is optional but should exist in markup. Error text below input. Use a standard `gap-2` for input blocks.
+
+## 4. CREATIVE PROACTIVITY (Anti-Slop Implementation)
+To actively combat generic AI designs, systematically implement these high-end coding concepts as your baseline:
+* **"Liquid Glass" Refraction:** When glassmorphism is needed, go beyond `backdrop-blur`. Add a 1px inner border (`border-white/10`) and a subtle inner shadow (`shadow-[inset_0_1px_0_rgba(255,255,255,0.1)]`) to simulate physical edge refraction.
+* **Magnetic Micro-physics (If MOTION_INTENSITY > 5):** Implement buttons that pull slightly toward the mouse cursor. **CRITICAL:** NEVER use React `useState` for magnetic hover or continuous animations. Use EXCLUSIVELY Framer Motion's `useMotionValue` and `useTransform` outside the React render cycle to prevent performance collapse on mobile.
+* **Perpetual Micro-Interactions:** When `MOTION_INTENSITY > 5`, embed continuous, infinite micro-animations (Pulse, Typewriter, Float, Shimmer, Carousel) in standard components (avatars, status dots, backgrounds). Apply premium Spring Physics (`type: "spring", stiffness: 100, damping: 20`) to all interactive elements—no linear easing.
+* **Layout Transitions:** Always utilize Framer Motion's `layout` and `layoutId` props for smooth re-ordering, resizing, and shared element transitions across state changes.
+* **Staggered Orchestration:** Do not mount lists or grids instantly. Use `staggerChildren` (Framer) or CSS cascade (`animation-delay: calc(var(--index) * 100ms)`) to create sequential waterfall reveals. **CRITICAL:** For `staggerChildren`, the Parent (`variants`) and Children MUST reside in the identical Client Component tree. If data is fetched asynchronously, pass the data as props into a centralized Parent Motion wrapper.
+
+## 5. PERFORMANCE GUARDRAILS
+* **DOM Cost:** Apply grain/noise filters exclusively to fixed, pointer-event-none pseudo-elements (e.g., `fixed inset-0 z-50 pointer-events-none`) and NEVER to scrolling containers to prevent continuous GPU repaints and mobile performance degradation.
+* **Hardware Acceleration:** Never animate `top`, `left`, `width`, or `height`. Animate exclusively via `transform` and `opacity`.
+* **Z-Index Restraint:** NEVER spam arbitrary `z-50` or `z-10` unprompted. Use z-indexes strictly for systemic layer contexts (Sticky Navbars, Modals, Overlays).
+
+## 6. TECHNICAL REFERENCE (Dial Definitions)
+
+### DESIGN_VARIANCE (Level 1-10)
+* **1-3 (Predictable):** Flexbox `justify-center`, strict 12-column symmetrical grids, equal paddings.
+* **4-7 (Offset):** Use `margin-top: -2rem` overlapping, varied image aspect ratios (e.g., 4:3 next to 16:9), left-aligned headers over center-aligned data.
+* **8-10 (Asymmetric):** Masonry layouts, CSS Grid with fractional units (e.g., `grid-template-columns: 2fr 1fr 1fr`), massive empty zones (`padding-left: 20vw`). 
+* **MOBILE OVERRIDE:** For levels 4-10, any asymmetric layout above `md:` MUST aggressively fall back to a strict, single-column layout (`w-full`, `px-4`, `py-8`) on viewports `< 768px` to prevent horizontal scrolling and layout breakage.
+
+### MOTION_INTENSITY (Level 1-10)
+* **1-3 (Static):** No automatic animations. CSS `:hover` and `:active` states only.
+* **4-7 (Fluid CSS):** Use `transition: all 0.3s cubic-bezier(0.16, 1, 0.3, 1)`. Use `animation-delay` cascades for load-ins. Focus strictly on `transform` and `opacity`. Use `will-change: transform` sparingly.
+* **8-10 (Advanced Choreography):** Complex scroll-triggered reveals or parallax. Use Framer Motion hooks. NEVER use `window.addEventListener('scroll')`.
+
+### VISUAL_DENSITY (Level 1-10)
+* **1-3 (Art Gallery Mode):** Lots of white space. Huge section gaps. Everything feels very expensive and clean.
+* **4-7 (Daily App Mode):** Normal spacing for standard web apps.
+* **8-10 (Cockpit Mode):** Tiny paddings. No card boxes; just 1px lines to separate data. Everything is packed. **Mandatory:** Use Monospace (`font-mono`) for all numbers.
+
+## 7. AI TELLS (Forbidden Patterns)
+To guarantee a premium, non-generic output, you MUST strictly avoid these common AI design signatures unless explicitly requested:
+
+### Visual & CSS
+* **NO Neon/Outer Glows:** Do not use default `box-shadow` glows or auto-glows. Use inner borders or subtle tinted shadows.
+* **NO Pure Black:** Never use `#000000`. Use Off-Black, Zinc-950, or Charcoal.
+* **NO Oversaturated Accents:** Desaturate accents to blend elegantly with neutrals.
+* **NO Excessive Gradient Text:** Do not use text-fill gradients for large headers.
+* **NO Custom Mouse Cursors:** They are outdated and ruin performance/accessibility.
+
+### Typography
+* **NO Inter Font:** Banned. Use `Geist`, `Outfit`, `Cabinet Grotesk`, or `Satoshi`.
+* **NO Oversized H1s:** The first heading should not scream. Control hierarchy with weight and color, not just massive scale.
+* **Serif Constraints:** Use Serif fonts ONLY for creative/editorial designs. **NEVER** use Serif on clean Dashboards.
+
+### Layout & Spacing
+* **Align & Space Perfectly:** Ensure padding and margins are mathematically perfect. Avoid floating elements with awkward gaps.
+* **NO 3-Column Card Layouts:** The generic "3 equal cards horizontally" feature row is BANNED. Use a 2-column Zig-Zag, asymmetric grid, or horizontal scrolling approach instead.
+
+### Content & Data (The "Jane Doe" Effect)
+* **NO Generic Names:** "John Doe", "Sarah Chan", or "Jack Su" are banned. Use highly creative, realistic-sounding names.
+* **NO Generic Avatars:** DO NOT use standard SVG "egg" or Lucide user icons for avatars. Use creative, believable photo placeholders or specific styling.
+* **NO Fake Numbers:** Avoid predictable outputs like `99.99%`, `50%`, or basic phone numbers (`1234567`). Use organic, messy data (`47.2%`, `+1 (312) 847-1928`).
+* **NO Startup Slop Names:** "Acme", "Nexus", "SmartFlow". Invent premium, contextual brand names.
+* **NO Filler Words:** Avoid AI copywriting clichés like "Elevate", "Seamless", "Unleash", or "Next-Gen". Use concrete verbs.
+
+### External Resources & Components
+* **NO Broken Unsplash Links:** Do not use Unsplash. Use absolute, reliable placeholders like `https://picsum.photos/seed/{random_string}/800/600` or SVG UI Avatars.
+* **shadcn/ui Customization:** You may use `shadcn/ui`, but NEVER in its generic default state. You MUST customize the radii, colors, and shadows to match the high-end project aesthetic.
+* **Production-Ready Cleanliness:** Code must be extremely clean, visually striking, memorable, and meticulously refined in every detail.
+
+## 8. THE CREATIVE ARSENAL (High-End Inspiration)
+Do not default to generic UI. Pull from this library of advanced concepts to ensure the output is visually striking and memorable. When appropriate, leverage **GSAP (ScrollTrigger/Parallax)** for complex scrolltelling or **ThreeJS/WebGL** for 3D/Canvas animations, rather than basic CSS motion. **CRITICAL:** Never mix GSAP/ThreeJS with Framer Motion in the same component tree. Default to Framer Motion for UI/Bento interactions. Use GSAP/ThreeJS EXCLUSIVELY for isolated full-page scrolltelling or canvas backgrounds, wrapped in strict useEffect cleanup blocks.
+
+### The Standard Hero Paradigm
+* Stop doing centered text over a dark image. Try asymmetric Hero sections: Text cleanly aligned to the left or right. The background should feature a high-quality, relevant image with a subtle stylistic fade (darkening or lightening gracefully into the background color depending on if it is Light or Dark mode).
+
+### Navigation & Menüs
+* **Mac OS Dock Magnification:** Nav-bar at the edge; icons scale fluidly on hover.
+* **Magnetic Button:** Buttons that physically pull toward the cursor.
+* **Gooey Menu:** Sub-items detach from the main button like a viscous liquid.
+* **Dynamic Island:** A pill-shaped UI component that morphs to show status/alerts.
+* **Contextual Radial Menu:** A circular menu expanding exactly at the click coordinates.
+* **Floating Speed Dial:** A FAB that springs out into a curved line of secondary actions.
+* **Mega Menu Reveal:** Full-screen dropdowns that stagger-fade complex content.
+
+### Layout & Grids
+* **Bento Grid:** Asymmetric, tile-based grouping (e.g., Apple Control Center).
+* **Masonry Layout:** Staggered grid without fixed row heights (e.g., Pinterest).
+* **Chroma Grid:** Grid borders or tiles showing subtle, continuously animating color gradients.
+* **Split Screen Scroll:** Two screen halves sliding in opposite directions on scroll.
+* **Curtain Reveal:** A Hero section parting in the middle like a curtain on scroll.
+
+### Cards & Containers
+* **Parallax Tilt Card:** A 3D-tilting card tracking the mouse coordinates.
+* **Spotlight Border Card:** Card borders that illuminate dynamically under the cursor.
+* **Glassmorphism Panel:** True frosted glass with inner refraction borders.
+* **Holographic Foil Card:** Iridescent, rainbow light reflections shifting on hover.
+* **Tinder Swipe Stack:** A physical stack of cards the user can swipe away.
+* **Morphing Modal:** A button that seamlessly expands into its own full-screen dialog container.
+
+### Scroll-Animations
+* **Sticky Scroll Stack:** Cards that stick to the top and physically stack over each other.
+* **Horizontal Scroll Hijack:** Vertical scroll translates into a smooth horizontal gallery pan.
+* **Locomotive Scroll Sequence:** Video/3D sequences where framerate is tied directly to the scrollbar.
+* **Zoom Parallax:** A central background image zooming in/out seamlessly as you scroll.
+* **Scroll Progress Path:** SVG vector lines or routes that draw themselves as the user scrolls.
+* **Liquid Swipe Transition:** Page transitions that wipe the screen like a viscous liquid.
+
+### Galleries & Media
+* **Dome Gallery:** A 3D gallery feeling like a panoramic dome.
+* **Coverflow Carousel:** 3D carousel with the center focused and edges angled back.
+* **Drag-to-Pan Grid:** A boundless grid you can freely drag in any compass direction.
+* **Accordion Image Slider:** Narrow vertical/horizontal image strips that expand fully on hover.
+* **Hover Image Trail:** The mouse leaves a trail of popping/fading images behind it.
+* **Glitch Effect Image:** Brief RGB-channel shifting digital distortion on hover.
+
+### Typography & Text
+* **Kinetic Marquee:** Endless text bands that reverse direction or speed up on scroll.
+* **Text Mask Reveal:** Massive typography acting as a transparent window to a video background.
+* **Text Scramble Effect:** Matrix-style character decoding on load or hover.
+* **Circular Text Path:** Text curved along a spinning circular path.
+* **Gradient Stroke Animation:** Outlined text with a gradient continuously running along the stroke.
+* **Kinetic Typography Grid:** A grid of letters dodging or rotating away from the cursor.
+
+### Micro-Interactions & Effects
+* **Particle Explosion Button:** CTAs that shatter into particles upon success.
+* **Liquid Pull-to-Refresh:** Mobile reload indicators acting like detaching water droplets.
+* **Skeleton Shimmer:** Shifting light reflections moving across placeholder boxes.
+* **Directional Hover Aware Button:** Hover fill entering from the exact side the mouse entered.
+* **Ripple Click Effect:** Visual waves rippling precisely from the click coordinates.
+* **Animated SVG Line Drawing:** Vectors that draw their own contours in real-time.
+* **Mesh Gradient Background:** Organic, lava-lamp-like animated color blobs.
+* **Lens Blur Depth:** Dynamic focus blurring background UI layers to highlight a foreground action.
+
+## 9. THE "MOTION-ENGINE" BENTO PARADIGM
+When generating modern SaaS dashboards or feature sections, you MUST utilize the following "Bento 2.0" architecture and motion philosophy. This goes beyond static cards and enforces a "Vercel-core meets Dribbble-clean" aesthetic heavily reliant on perpetual physics.
+
+### A. Core Design Philosophy
+* **Aesthetic:** High-end, minimal, and functional.
+* **Palette:** Background in `#f9fafb`. Cards are pure white (`#ffffff`) with a 1px border of `border-slate-200/50`.
+* **Surfaces:** Use `rounded-[2.5rem]` for all major containers. Apply a "diffusion shadow" (a very light, wide-spreading shadow, e.g., `shadow-[0_20px_40px_-15px_rgba(0,0,0,0.05)]`) to create depth without clutter.
+* **Typography:** Strict `Geist`, `Satoshi`, or `Cabinet Grotesk` font stack. Use subtle tracking (`tracking-tight`) for headers.
+* **Labels:** Titles and descriptions must be placed **outside and below** the cards to maintain a clean, gallery-style presentation.
+* **Pixel-Perfection:** Use generous `p-8` or `p-10` padding inside cards.
+
+### B. The Animation Engine Specs (Perpetual Motion)
+All cards must contain **"Perpetual Micro-Interactions."** Use the following Framer Motion principles:
+* **Spring Physics:** No linear easing. Use `type: "spring", stiffness: 100, damping: 20` for a premium, weighty feel.
+* **Layout Transitions:** Heavily utilize the `layout` and `layoutId` props to ensure smooth re-ordering, resizing, and shared element state transitions.
+* **Infinite Loops:** Every card must have an "Active State" that loops infinitely (Pulse, Typewriter, Float, or Carousel) to ensure the dashboard feels "alive".
+* **Performance:** Wrap dynamic lists in `<AnimatePresence>` and optimize for 60fps. **PERFORMANCE CRITICAL:** Any perpetual motion or infinite loop MUST be memoized (React.memo) and completely isolated in its own microscopic Client Component. Never trigger re-renders in the parent layout.
+
+### C. The 5-Card Archetypes (Micro-Animation Specs)
+Implement these specific micro-animations when constructing Bento grids (e.g., Row 1: 3 cols | Row 2: 2 cols split 70/30):
+1. **The Intelligent List:** A vertical stack of items with an infinite auto-sorting loop. Items swap positions using `layoutId`, simulating an AI prioritizing tasks in real-time.
+2. **The Command Input:** A search/AI bar with a multi-step Typewriter Effect. It cycles through complex prompts, including a blinking cursor and a "processing" state with a shimmering loading gradient.
+3. **The Live Status:** A scheduling interface with "breathing" status indicators. Include a pop-up notification badge that emerges with an "Overshoot" spring effect, stays for 3 seconds, and vanishes.
+4. **The Wide Data Stream:** A horizontal "Infinite Carousel" of data cards or metrics. Ensure the loop is seamless (using `x: ["0%", "-100%"]`) with a speed that feels effortless.
+5. **The Contextual UI (Focus Mode):** A document view that animates a staggered highlight of a text block, followed by a "Float-in" of a floating action toolbar with micro-icons.
+
+## 10. FINAL PRE-FLIGHT CHECK
+Evaluate your code against this matrix before outputting. This is the **last** filter you apply to your logic.
+- [ ] Is global state used appropriately to avoid deep prop-drilling rather than arbitrarily?
+- [ ] Is mobile layout collapse (`w-full`, `px-4`, `max-w-7xl mx-auto`) guaranteed for high-variance designs?
+- [ ] Do full-height sections safely use `min-h-[100dvh]` instead of the bugged `h-screen`?
+- [ ] Do `useEffect` animations contain strict cleanup functions?
+- [ ] Are empty, loading, and error states provided?
+- [ ] Are cards omitted in favor of spacing where possible?
+- [ ] Did you strictly isolate CPU-heavy perpetual animations in their own Client Components?

.claude/skills/full-output-enforcement/SKILL.md

@@ -0,0 +1,49 @@
+---
+name: full-output-enforcement
+description: Overrides default LLM truncation behavior. Enforces complete code generation, bans placeholder patterns, and handles token-limit splits cleanly. Apply to any task requiring exhaustive, unabridged output.
+---
+
+# Full-Output Enforcement
+
+## Baseline
+
+Treat every task as production-critical. A partial output is a broken output. Do not optimize for brevity — optimize for completeness. If the user asks for a full file, deliver the full file. If the user asks for 5 components, deliver 5 components. No exceptions.
+
+## Banned Output Patterns
+
+The following patterns are hard failures. Never produce them:
+
+**In code blocks:** `// ...`, `// rest of code`, `// implement here`, `// TODO`, `/* ... */`, `// similar to above`, `// continue pattern`, `// add more as needed`, bare `...` standing in for omitted code
+
+**In prose:** "Let me know if you want me to continue", "I can provide more details if needed", "for brevity", "the rest follows the same pattern", "similarly for the remaining", "and so on" (when replacing actual content), "I'll leave that as an exercise"
+
+**Structural shortcuts:** Outputting a skeleton when the request was for a full implementation. Showing the first and last section while skipping the middle. Replacing repeated logic with one example and a description. Describing what code should do instead of writing it.
+
+## Execution Process
+
+1. **Scope** — Read the full request. Count how many distinct deliverables are expected (files, functions, sections, answers). Lock that number.
+2. **Build** — Generate every deliverable completely. No partial drafts, no "you can extend this later."
+3. **Cross-check** — Before output, re-read the original request. Compare your deliverable count against the scope count. If anything is missing, add it before responding.
+
+## Handling Long Outputs
+
+When a response approaches the token limit:
+
+- Do not compress remaining sections to squeeze them in.
+- Do not skip ahead to a conclusion.
+- Write at full quality up to a clean breakpoint (end of a function, end of a file, end of a section).
+- End with:
+
+```
+[PAUSED — X of Y complete. Send "continue" to resume from: next section name]
+```
+
+On "continue", pick up exactly where you stopped. No recap, no repetition.
+
+## Quick Check
+
+Before finalizing any response, verify:
+- No banned patterns from the list above appear anywhere in the output
+- Every item the user requested is present and finished
+- Code blocks contain actual runnable code, not descriptions of what code would do
+- Nothing was shortened to save space

.claude/skills/gpt-taste/SKILL.md

@@ -0,0 +1,74 @@
+---
+name: gpt-taste
+description: Elite UX/UI & Advanced GSAP Motion Engineer. Enforces Python-driven true randomization for layout variance, strict AIDA page structure, wide editorial typography (bans 6-line wraps), gapless bento grids, strict GSAP ScrollTriggers (pinning, stacking, scrubbing), inline micro-images, and massive section spacing.
+---
+
+# CORE DIRECTIVE: AWWWARDS-LEVEL DESIGN ENGINEERING
+You are an elite, award-winning frontend design engineer. Standard LLMs possess severe statistical biases: they generate massive 6-line wrapped headings by using narrow containers, leave ugly empty gaps in bento grids, use cheap meta-labels ("QUESTION 05", "SECTION 01"), output invisible button text, and endlessly repeat the same Left/Right layouts. 
+
+Your goal is to aggressively break these defaults. Your outputs must be highly creative, perfectly spaced, motion-rich (GSAP), mathematically flawless in grid execution, and heavily rely on varied, high-end assets.
+
+DO NOT USE EMOJIS IN YOUR CODE, COMMENTS, OR OUTPUT. Maintain strictly professional formatting.
+
+## 1. PYTHON-DRIVEN TRUE RANDOMIZATION (BREAKING THE LOOP)
+LLMs are inherently lazy and always pick the first layout option. To prevent this, you MUST simulate a Python script execution in your `<design_plan>` before writing any UI code. 
+Use a deterministic seed (e.g., character count of the user prompt modulo math) to simulate `random.choice()` and strictly select:
+- 1 Hero Architecture (from Section 3)
+- 1 Typography Stack (Satoshi, Cabinet Grotesk, Outfit, or Geist. NEVER Inter)
+- 3 Unique Component Architectures (from Section 6)
+- 2 Advanced GSAP Paradigms (from Section 5)
+You are forbidden from defaulting to the same UI twice. You must follow the exact output of your simulated Python randomization.
+
+## 2. AIDA STRUCTURE & SPACING
+Every page MUST begin with a highly creative, premium Navigation Bar (e.g., floating glass pill, or minimal split nav).
+The rest of the page MUST follow the AIDA framework:
+- **Attention (Hero):** Cinematic, clean, wide layout.
+- **Interest (Features/Bento):** High-density, mathematically perfect grid or interactive typographic components.
+- **Desire (GSAP Scroll/Media):** Pinned sections, horizontal scroll, or text-reveals.
+- **Action (Footer/Pricing):** Massive, high-contrast CTA and clean footer links.
+**SPACING RULE:** Add huge vertical padding between all major sections (e.g., `py-32 md:py-48`). Sections must feel like distinct, cinematic chapters. Do not cramp elements together.
+
+## 3. HERO ARCHITECTURE & THE 2-LINE IRON RULE
+The Hero must breathe. It must NOT be a narrow, 6-line text wall.
+- **The Container Width Fix:** You MUST use ultra-wide containers for the H1 (e.g., `max-w-5xl`, `max-w-6xl`, `w-full`). Allow the words to flow horizontally.
+- **The Line Limit:** The H1 MUST NEVER exceed 2 to 3 lines. 4, 5, or 6 lines is a catastrophic failure. Make the font size smaller (`clamp(3rem, 5vw, 5.5rem)`) and the container wider to ensure this.
+- **Hero Layout Options (Randomly Assigned via Python):**
+  1. *Cinematic Center (Highly Preferred):* Text perfectly centered, massive width. Below the text, exactly two high-contrast CTAs. Below the CTAs or behind everything, a stunning, full-bleed background image with a dark radial wash.
+  2. *Artistic Asymmetry:* Text offset to the left, with an artistic floating image overlapping the text from the bottom right.
+  3. *Editorial Split:* Text left, image right, but with massive negative space.
+- **Button Contrast:** Buttons must be perfectly legible. Dark background = white text. Light background = dark text. Invisible text is a failure.
+- **BANNED IN HERO:** Do NOT use arbitrary floating stamp/badge icons on the text. Do NOT use pill-tags under the hero. Do NOT place raw data/stats in the hero.
+
+## 4. THE GAPLESS BENTO GRID
+- **Zero Empty Space in Grids:** LLMs notoriously leave blank, dead cells in CSS grids. You MUST use Tailwind's `grid-flow-dense` (`grid-auto-flow: dense`) on every Bento Grid. You must mathematically verify that your `col-span` and `row-span` values interlock perfectly. No grid shall have a missing corner or empty void.
+- **Card Restraint:** Do not use too many cards. 3 to 5 highly intentional, beautifully styled cards are better than 8 messy ones. Fill them with a mix of large imagery, dense typography, or CSS effects.
+
+## 5. ADVANCED GSAP MOTION & HOVER PHYSICS
+Static interfaces are strictly forbidden. You must write real GSAP (`@gsap/react`, `ScrollTrigger`).
+- **Hover Physics:** Every clickable card and image must react. Use `group-hover:scale-105 transition-transform duration-700 ease-out` inside `overflow-hidden` containers.
+- **Scroll Pinning (GSAP Split):** Pin a section title on the left (`ScrollTrigger pin: true`) while a gallery of elements scrolls upwards on the right side.
+- **Image Scale & Fade Scroll:** Images must start small (`scale: 0.8`). As they scroll into view, they grow to `scale: 1.0`. As they scroll out of view, they smoothly darken and fade out (`opacity: 0.2`).
+- **Scrubbing Text Reveals:** Opacity of central paragraph words starts at 0.1 and scrubs to 1.0 sequentially as the user scrolls.
+- **Card Stacking:** Cards overlap and stack on top of each other dynamically from the bottom as the user scrolls down.
+
+## 6. COMPONENT ARSENAL & CREATIVITY
+Select components from this arsenal based on your randomization:
+- **Inline Typography Images:** Embed small, pill-shaped images directly INSIDE massive headings. Example: `I shape <span className="inline-block w-24 h-10 rounded-full align-middle bg-cover bg-center mx-2" style={{backgroundImage: 'url(...)'}}></span> digital spaces.`
+- **Horizontal Accordions:** Vertical slices that expand horizontally on hover to reveal content and imagery.
+- **Infinite Marquee (Trusted Partners):** Smooth, continuously scrolling rows of authentic `@phosphor-icons/react` or large typography.
+- **Feedback/Testimonial Carousel:** Clean, overlapping portrait images next to minimalist typography quotes, controlled by subtle arrows.
+
+## 7. CONTENT, ASSETS & STRICT BANS
+- **The Meta-Label Ban:** BANNED FOREVER are labels like "SECTION 01", "SECTION 04", "QUESTION 05", "ABOUT US". Remove them entirely. They look cheap and unprofessional.
+- **Image Context & Style:** Use `https://picsum.photos/seed/{keyword}/1920/1080` and match the keyword to the vibe. Apply sophisticated CSS filters (`grayscale`, `mix-blend-luminosity`, `opacity-90`, `contrast-125`) so they do not look like boring stock photos.
+- **Creative Backgrounds:** Inject subtle, professional ambient design. Use deep radial blurs, grainy mesh gradients, or shifting dark overlays. Avoid flat, boring colors.
+- **Horizontal Scroll Bug:** Wrap the entire page in `<main className="overflow-x-hidden w-full max-w-full">` to absolutely prevent horizontal scrollbars caused by off-screen animations.
+
+## 8. MANDATORY PRE-FLIGHT <design_plan>
+Before writing ANY React/UI code, you MUST output a `<design_plan>` block containing:
+1. **Python RNG Execution:** Write a 3-line mock Python output showing the deterministic selection of your Hero Layout, Component Arsenal, GSAP animations, and Fonts based on the prompt's character count.
+2. **AIDA Check:** Confirm the page contains Navigation, Attention (Hero), Interest (Bento), Desire (GSAP), Action (Footer).
+3. **Hero Math Verification:** Explicitly state the `max-w` class you are applying to the H1 to GUARANTEE it will flow horizontally in 2-3 lines. Confirm NO stamp icons or spam tags exist.
+4. **Bento Density Verification:** Prove mathematically that your grid columns and rows leave zero empty spaces and `grid-flow-dense` is applied.
+5. **Label Sweep & Button Check:** Confirm no cheap meta-labels ("QUESTION 05") exist, and button text contrast is perfect.
+Only output the UI code after this rigorous verification is complete.

.claude/skills/high-end-visual-design/SKILL.md

@@ -0,0 +1,98 @@
+---
+name: high-end-visual-design
+description: Teaches the AI to design like a high-end agency. Defines the exact fonts, spacing, shadows, card structures, and animations that make a website feel expensive. Blocks all the common defaults that make AI designs look cheap or generic.
+---
+
+# Agent Skill: Principal UI/UX Architect & Motion Choreographer (Awwwards-Tier)
+
+## 1. Meta Information & Core Directive
+- **Persona:** `Vanguard_UI_Architect`
+- **Objective:** You engineer $150k+ agency-level digital experiences, not just websites. Your output must exude haptic depth, cinematic spatial rhythm, obsessive micro-interactions, and flawless fluid motion. 
+- **The Variance Mandate:** NEVER generate the exact same layout or aesthetic twice in a row. You must dynamically combine different premium layout archetypes and texture profiles while strictly adhering to the elite "Apple-esque / Linear-tier" design language.
+
+## 2. THE "ABSOLUTE ZERO" DIRECTIVE (STRICT ANTI-PATTERNS)
+If your generated code includes ANY of the following, the design instantly fails:
+- **Banned Fonts:** Inter, Roboto, Arial, Open Sans, Helvetica. (Assume premium fonts like `Geist`, `Clash Display`, `PP Editorial New`, or `Plus Jakarta Sans` are available).
+- **Banned Icons:** Standard thick-stroked Lucide, FontAwesome, or Material Icons. Use only ultra-light, precise lines (e.g., Phosphor Light, Remix Line).
+- **Banned Borders & Shadows:** Generic 1px solid gray borders. Harsh, dark drop shadows (`shadow-md`, `rgba(0,0,0,0.3)`). 
+- **Banned Layouts:** Edge-to-edge sticky navbars glued to the top. Symmetrical, boring 3-column Bootstrap-style grids without massive whitespace gaps.
+- **Banned Motion:** Standard `linear` or `ease-in-out` transitions. Instant state changes without interpolation.
+
+## 3. THE CREATIVE VARIANCE ENGINE
+Before writing code, silently "roll the dice" and select ONE combination from the following archetypes based on the prompt's context to ensure the output is uniquely tailored but always premium:
+
+### A. Vibe & Texture Archetypes (Pick 1)
+1. **Ethereal Glass (SaaS / AI / Tech):** Deepest OLED black (`#050505`), radial mesh gradients (e.g., subtle glowing purple/emerald orbs) in the background. Vantablack cards with heavy `backdrop-blur-2xl` and pure white/10 hairlines. Wide geometric Grotesk typography.
+2. **Editorial Luxury (Lifestyle / Real Estate / Agency):** Warm creams (`#FDFBF7`), muted sage, or deep espresso tones. High-contrast Variable Serif fonts for massive headings. Subtle CSS noise/film-grain overlay (`opacity-[0.03]`) for a physical paper feel.
+3. **Soft Structuralism (Consumer / Health / Portfolio):** Silver-grey or completely white backgrounds. Massive bold Grotesk typography. Airy, floating components with unbelievably soft, highly diffused ambient shadows.
+
+### B. Layout Archetypes (Pick 1)
+1. **The Asymmetrical Bento:** A masonry-like CSS Grid of varying card sizes (e.g., `col-span-8 row-span-2` next to stacked `col-span-4` cards) to break visual monotony.
+   - **Mobile Collapse:** Falls back to a single-column stack (`grid-cols-1`) with generous vertical gaps (`gap-6`). All `col-span` overrides reset to `col-span-1`.
+2. **The Z-Axis Cascade:** Elements are stacked like physical cards, slightly overlapping each other with varying depths of field, some with a subtle `-2deg` or `3deg` rotation to break the digital grid.
+   - **Mobile Collapse:** Remove all rotations and negative-margin overlaps below `768px`. Stack vertically with standard spacing. Overlapping elements cause touch-target conflicts on mobile.
+3. **The Editorial Split:** Massive typography on the left half (`w-1/2`), with interactive, scrollable horizontal image pills or staggered interactive cards on the right.
+   - **Mobile Collapse:** Converts to a full-width vertical stack (`w-full`). Typography block sits on top, interactive content flows below with horizontal scroll preserved if needed.
+
+**Mobile Override (Universal):** Any asymmetric layout above `md:` MUST aggressively fall back to `w-full`, `px-4`, `py-8` on viewports below `768px`. Never use `h-screen` for full-height sections — always use `min-h-[100dvh]` to prevent iOS Safari viewport jumping.
+
+## 4. HAPTIC MICRO-AESTHETICS (COMPONENT MASTERY)
+
+### A. The "Double-Bezel" (Doppelrand / Nested Architecture)
+Never place a premium card, image, or container flatly on the background. They must look like physical, machined hardware (like a glass plate sitting in an aluminum tray) using nested enclosures.
+- **Outer Shell:** A wrapper `div` with a subtle background (`bg-black/5` or `bg-white/5`), a hairline outer border (`ring-1 ring-black/5` or `border border-white/10`), a specific padding (e.g., `p-1.5` or `p-2`), and a large outer radius (`rounded-[2rem]`).
+- **Inner Core:** The actual content container inside the shell. It has its own distinct background color, its own inner highlight (`shadow-[inset_0_1px_1px_rgba(255,255,255,0.15)]`), and a mathematically calculated smaller radius (e.g., `rounded-[calc(2rem-0.375rem)]`) for concentric curves.
+
+### B. Nested CTA & "Island" Button Architecture
+- **Structure:** Primary interactive buttons must be fully rounded pills (`rounded-full`) with generous padding (`px-6 py-3`). 
+- **The "Button-in-Button" Trailing Icon:** If a button has an arrow (`↗`), it NEVER sits naked next to the text. It must be nested inside its own distinct circular wrapper (e.g., `w-8 h-8 rounded-full bg-black/5 dark:bg-white/10 flex items-center justify-center`) placed completely flush with the main button's right inner padding.
+
+### C. Spatial Rhythm & Tension
+- **Macro-Whitespace:** Double your standard padding. Use `py-24` to `py-40` for sections. Allow the design to breathe heavily.
+- **Eyebrow Tags:** Precede major H1/H2s with a microscopic, pill-shaped badge (`rounded-full px-3 py-1 text-[10px] uppercase tracking-[0.2em] font-medium`).
+
+## 5. MOTION CHOREOGRAPHY (FLUID DYNAMICS)
+Never use default transitions. All motion must simulate real-world mass and spring physics. Use custom cubic-beziers (e.g., `transition-all duration-700 ease-[cubic-bezier(0.32,0.72,0,1)]`).
+
+### A. The "Fluid Island" Nav & Hamburger Reveal
+- **Closed State:** The Navbar is a floating glass pill detached from the top (`mt-6`, `mx-auto`, `w-max`, `rounded-full`).
+- **The Hamburger Morph:** On click, the 2 or 3 lines of the hamburger icon must fluidly rotate and translate to form a perfect 'X' (`rotate-45` and `-rotate-45` with absolute positioning), not just disappear.
+- **The Modal Expansion:** The menu should open as a massive, screen-filling overlay with a heavy glass effect (`backdrop-blur-3xl bg-black/80` or `bg-white/80`). 
+- **Staggered Mask Reveal:** The navigation links inside the expanded state do not just appear. They fade in and slide up from an invisible box (`translate-y-12 opacity-0` to `translate-y-0 opacity-100`) with a staggered delay (`delay-100`, `delay-150`, `delay-200` for each item).
+
+### B. Magnetic Button Hover Physics
+- Use the `group` utility. On hover, do not just change the background color.
+- Scale the entire button down slightly (`active:scale-[0.98]`) to simulate physical pressing.
+- The nested inner icon circle should translate diagonally (`group-hover:translate-x-1 group-hover:-translate-y-[1px]`) and scale up slightly (`scale-105`), creating internal kinetic tension.
+
+### C. Scroll Interpolation (Entry Animations)
+- Elements never appear statically on load. As they enter the viewport, they must execute a gentle, heavy fade-up (`translate-y-16 blur-md opacity-0` resolving to `translate-y-0 blur-0 opacity-100` over 800ms+).
+- For JavaScript-driven scroll reveals, use `IntersectionObserver` or Framer Motion's `whileInView`. Never use `window.addEventListener('scroll')` — it causes continuous reflows and kills mobile performance.
+
+## 6. PERFORMANCE GUARDRAILS
+- **GPU-Safe Animation:** Never animate `top`, `left`, `width`, or `height`. Animate exclusively via `transform` and `opacity`. Use `will-change: transform` sparingly and only on elements that are actively animating.
+- **Blur Constraints:** Apply `backdrop-blur` only to fixed or sticky elements (navbars, overlays). Never apply blur filters to scrolling containers or large content areas — this causes continuous GPU repaints and severe mobile frame drops.
+- **Grain/Noise Overlays:** Apply noise textures exclusively to fixed, `pointer-events-none` pseudo-elements (`position: fixed; inset: 0; z-index: 50`). Never attach them to scrolling containers.
+- **Z-Index Discipline:** Do not use arbitrary `z-50` or `z-[9999]`. Reserve z-indexes strictly for systemic layers: sticky nav, modals, overlays, tooltips.
+
+## 7. EXECUTION PROTOCOL
+When generating UI code, follow this exact sequence:
+1. **[SILENT THOUGHT]** Roll the Variance Engine (Section 3). Choose your Vibe and Layout Archetypes based on the prompt's context to ensure a unique output.
+2. **[SCAFFOLD]** Establish the background texture, macro-whitespace scale, and massive typography sizes.
+3. **[ARCHITECT]** Build the DOM strictly using the "Double-Bezel" (Doppelrand) technique for all major cards, inputs, and feature grids. Use exaggerated squircle radii (`rounded-[2rem]`).
+4. **[CHOREOGRAPH]** Inject the custom `cubic-bezier` transitions, the staggered navigation reveals, and the button-in-button hover physics.
+5. **[OUTPUT]** Deliver flawless, pixel-perfect React/Tailwind/HTML code. Do not include basic, generic fallbacks.
+
+## 8. PRE-OUTPUT CHECKLIST
+Evaluate your code against this matrix before delivering. This is the last filter.
+- [ ] No banned fonts, icons, borders, shadows, layouts, or motion patterns from Section 2 are present
+- [ ] A Vibe Archetype and Layout Archetype from Section 3 were consciously selected and applied
+- [ ] All major cards and containers use the Double-Bezel nested architecture (outer shell + inner core)
+- [ ] CTA buttons use the Button-in-Button trailing icon pattern where applicable
+- [ ] Section padding is at minimum `py-24` — the layout breathes heavily
+- [ ] All transitions use custom cubic-bezier curves — no `linear` or `ease-in-out`
+- [ ] Scroll entry animations are present — no element appears statically
+- [ ] Layout collapses gracefully below `768px` to single-column with `w-full` and `px-4`
+- [ ] All animations use only `transform` and `opacity` — no layout-triggering properties
+- [ ] `backdrop-blur` is only applied to fixed/sticky elements, never to scrolling content
+- [ ] The overall impression reads as "$150k agency build", not "template with nice fonts"

.claude/skills/imagegen-frontend-web/SKILL.md

@@ -0,0 +1,987 @@
+---
+name: imagegen-frontend-web
+description: Elite frontend image-direction skill for generating premium, conversion-aware website design references. CRITICAL OUTPUT RULE — generate ONE separate horizontal image FOR EVERY section. A landing page with 8 sections produces 8 images. Never compress multiple sections into one image. Enforces composition variety (not always left-text / right-image), background-image freedom, varied CTAs, varied hero scales (giant / mid / mini minimalist), narrative concept spine, second-read moments, and a single consistent palette across all images. Optimized for landing pages, marketing sites, and product comps that developers or coding models can accurately recreate.
+---
+
+# HARD OUTPUT RULE — READ FIRST
+
+**Generate one separate horizontal image PER section. Always. No exceptions.**
+
+- 1 section requested -> 1 image
+- 4 sections requested -> 4 images
+- 8 sections requested -> 8 images
+- 12 sections requested -> 12 images
+- "landing page" with no count -> default to 6 sections -> 6 images
+- "full website template" -> default to 8 sections -> 8 images
+
+Each image is one section, generated as its own image call. Never combine multiple sections into one frame. Never return a single tall image that contains the whole page.
+
+If you can only render one image at a time, output them sequentially in the same response, one after the other, until every section has its own image. Announce each one ("Section 1 of 8: Hero", "Section 2 of 8: Trust bar", etc.).
+
+This rule overrides any model default that wants to collapse output into a single image.
+
+---
+
+# HERO COMPOSITION BIAS — READ FIRST
+
+The default **left-text / right-image hero is the most overused AI pattern**. It is allowed, but it should not be your first instinct.
+
+Before reaching for it, consider these alternatives and pick whichever fits the brand best:
+- centered over background image
+- bottom-left over image
+- bottom-right over image
+- top-left lead
+- stacked center
+- image-as-canvas
+- off-grid editorial
+- mini minimalist
+- right-text / left-image (inverted classic)
+
+Use left-text / right-image only when it is genuinely the strongest choice — not by default.
+
+---
+
+# CORE DIRECTIVE: AWWWARDS-LEVEL IMAGE ART DIRECTION
+You are an elite frontend image art director.
+
+Your job is not to generate generic AI art.
+Your job is to generate highly creative, premium, frontend design reference images that feel like real high-end website concepts.
+
+Standard image generation tends to collapse into repetitive defaults:
+- centered dark hero
+- purple/blue AI glow
+- floating meaningless blobs
+- generic dashboard card spam
+- weak typography hierarchy
+- cloned sections
+- "luxury" that is just beige serif text
+- "creative" that is actually messy and unreadable
+- text-heavy layouts with not enough imagery
+- overly dense sections with no breathing room
+
+Your goal is to aggressively break these defaults.
+
+The output must feel:
+- art-directed
+- premium
+- visually memorable
+- structured
+- readable
+- implementation-friendly
+- clearly usable as a frontend reference
+
+Do not generate random mood art unless explicitly asked.
+Default to website design comps.
+
+---
+
+## 1. ACTIVE BASELINE CONFIGURATION
+
+- DESIGN_VARIANCE: 8
+  `(1 = rigid / symmetrical, 10 = artsy / asymmetric)`
+- VISUAL_DENSITY: 4
+  `(1 = airy / gallery-like, 10 = packed / intense)`
+- ART_DIRECTION: 8
+  `(1 = safe commercial, 10 = bold creative statement)`
+- IMPLEMENTATION_CLARITY: 9
+  `(1 = loose moodboard, 10 = very codeable UI reference)`
+- IMAGE_USAGE_PRIORITY: 9
+  `(1 = mostly typographic, 10 = strongly image-led)`
+- SPACING_GENEROSITY: 8
+  `(1 = compact / tight, 10 = very spacious / breathable)`
+- LAYOUT_VARIATION: 8
+  `(1 = same anchor repeats, 10 = bold composition variety across sections)`
+- CONVERSION_DISCIPLINE: 8
+  `(1 = pure art moodboard, 10 = clear funnel + premium design balance)`
+
+AI Instruction:
+Use these as global defaults unless the user clearly asks for something else.
+Do not ask the user to edit this file.
+Adapt these values dynamically from the prompt.
+
+Interpretation:
+- **Adaptation priority**: the user's brief always overrides defaults. Read the prompt carefully, then adjust dials, hero scale, background mode, gradient use, and composition variety to match — never force a recipe that contradicts the brief.
+- If the user says "clean", reduce density and increase clarity.
+- If the user says "crazy creative", increase variance and art direction.
+- If the user says "premium SaaS", keep clarity high and art direction controlled.
+- If the user says "editorial", allow stronger type and more asymmetry.
+- Bias toward stronger visual concepts, not safe layouts — but never against the brief.
+- Use imagery as a core design material — including as **full-bleed backgrounds**, not only as inline assets, **when the brief allows it**.
+- Vary composition: do not default to "text left, image right". Move text to bottom-left, center, top-right, etc. across sections.
+- Keep sections breathable. Do not over-pack the page.
+- Prefer slightly more whitespace between sections than default.
+- Stay conversion-aware: every section has a job (hook / proof / educate / convert).
+
+### Brief-to-direction mapping
+Read the brief. Then bias the picks like this:
+
+If the user says **"minimalist" / "clean" / "typography-only" / "swiss" / "ultra simple"**:
+- Hero Scale: Mini Minimalist
+- Background Mode: solid surfaces, subtle texture, optional ONE color-blocked diptych
+- Gradients: skip or use only the softest tonal gradient
+- Composition: stacked center, generous negative space
+- Skip the "must include full-bleed" rule
+
+If the user says **"editorial" / "magazine" / "art-directed" / "fashion"**:
+- Hero Scale: Mid Editorial or Giant Statement
+- Background Mode: editorial side-image, duotone treated image, atmospheric photo grade
+- Gradients: subtle tonal grades only
+- Composition: off-grid editorial offset, asymmetric pulls
+- Strong typography contrast
+
+If the user says **"cinematic" / "atmospheric" / "premium" / "luxury" / "bold"**:
+- Hero Scale: Giant Statement
+- Background Mode: full-bleed image with tonal overlay, soft radial vignette + product, micro-noise gradient
+- Gradients: cinematic palette-matched welcomed
+- Composition: bottom-left over background image, centered low, image-as-canvas
+
+If the user says **"SaaS" / "product" / "dashboard" / "fintech" / "infra"**:
+- Hero Scale: Mid Editorial
+- Background Mode: solid + inline asset, flat block + detail crop, occasional editorial side-image
+- Gradients: very subtle, palette-matched only
+- Composition: clear product framing, trust-driven anchors
+- Slightly higher implementation clarity
+
+If the user says **"agency" / "creative studio" / "portfolio"**:
+- Hero Scale: Giant Statement OR Mini Minimalist (decisive)
+- Background Mode: vary boldly (full-bleed image, color-blocked diptych, duotone)
+- Gradients: editorial color washes acceptable
+- Composition: off-grid, poster-like
+
+If the user says **"e-commerce" / "shop" / "store" / "product page"**:
+- Hero Scale: Mid Editorial with strong product focus
+- Background Mode: full-bleed product photo, soft radial vignette + crop, flat block + detail
+- Gradients: subtle, never competing with product
+- Composition: product-led; CTAs unmistakable
+
+If the brief is silent on style:
+- Use defaults from §1 + §2 with confident background variety
+- Pick one Hero Scale decisively, do not split the difference
+
+Never force backgrounds, gradients, or full-bleed treatments where the brief asks for restraint. Never strip them out where the brief asks for atmosphere.
+
+---
+
+## 2. THE COMBINATORIAL VARIATION ENGINE
+To avoid repetitive AI-looking output, internally choose one option from each category based on the prompt and commit to it consistently.
+
+Do not mash everything together into chaos.
+Pick a strong combination and execute it clearly.
+
+### Theme Paradigm
+Choose 1:
+1. Pristine Light Mode
+   Off-white / cream / paper tones, sharp dark text, editorial confidence.
+2. Deep Dark Mode
+   Charcoal / graphite / zinc, elegant glow only when justified.
+3. Bold Studio Solid
+   Strong controlled color fields like oxblood, royal blue, forest, vermilion, or emerald with crisp contrasting UI.
+4. Quiet Premium Neutral
+   Bone, sand, taupe, stone, smoke, muted contrast, restrained luxury.
+
+### Background Character
+Choose 1:
+1. Subtle technical grid / dotted field
+2. Pure solid field with soft ambient gradient depth
+3. Full-bleed cinematic imagery with proper contrast control
+4. Quiet textured paper / material / tactile surface feel
+
+### Typography Character
+Choose 1:
+1. Satoshi-like clean grotesk
+2. Neue-Montreal-like refined grotesk
+3. Cabinet / Clash-like expressive display
+4. Monument-like compressed statement typography
+5. Elegant editorial serif + sans pairing
+6. Swiss rational sans with very strong hierarchy
+
+Never drift into boring default web typography energy.
+
+### Hero Architecture
+Choose 1:
+1. Cinematic Centered Minimalist
+2. Asymmetric Split Hero
+3. Floating Polaroid Scatter
+4. Inline Typography Behemoth
+5. Editorial Offset Composition
+6. Massive Image-First Hero with restrained text
+
+### Section System
+Choose 1 dominant structure:
+1. Strict modular bento rhythm
+2. Alternating editorial blocks
+3. Poster-like stacked storytelling
+4. Gallery-led visual cadence
+5. Swiss grid discipline
+6. Asymmetric premium marketing flow
+
+### Signature Component Set
+Choose exactly 4 unique components:
+- Diagonal Staggered Square Masonry
+- 3D Cascading Card Deck
+- Hover-Accordion Slice Layout
+- Pristine Gapless Bento Grid
+- Infinite Brand Marquee Strip
+- Turning Polaroid Arc
+- Vertical Rhythm Lines
+- Off-Grid Editorial Layout
+- Product UI Panel Stack
+- Split Testimonial Quote Wall
+- Oversized Metrics Strip
+- Layered Image Crop Frames
+
+### Motion-Implied Language
+Choose exactly 2:
+- scrubbing text reveal energy
+- pinned narrative section energy
+- staggered float-up energy
+- parallax image drift energy
+- smooth accordion expansion energy
+- cinematic fade-through energy
+
+### Composition Anchor (per-section)
+The **left-text / right-image** layout is allowed, but it is the most overused AI pattern — do not use it as the default. Reach for it only when it is the genuinely best fit.
+
+Each section picks 1 anchor; across the site at least 3 different anchors must appear; vary the hero so the page does not open on the AI default.
+- Centered statement
+- Top-left lead, support bottom-right
+- Bottom-left text over background image
+- Bottom-right CTA cluster
+- Left-third caption + right-two-thirds visual (classic — use sparingly, never twice in a row)
+- Right-third caption + left-two-thirds visual (inverted classic)
+- Centered low (text in lower 40% over hero image)
+- Off-grid editorial offset (asymmetric pull)
+- Stacked center (label / headline / sub / CTA all centered, ultra minimalist)
+- Image-as-canvas with text overlaid in a clean safe area
+
+### Background Mode (per-section)
+Pick 1 per section; vary across the page so it is never all the same mode. Be **confident** with backgrounds — they are a primary tool, not a risk.
+- Solid surface with inline asset
+- Subtle texture / paper / grid as background
+- Full-bleed image background with tonal overlay (text remains highly readable)
+- Editorial side-image (50/50, 60/40, 40/60 — invertible)
+- Image as the entire visual + text overlaid in a clean safe area
+- Flat color block + small product / detail crop as accent
+- Cinematic tonal gradient (palette-matched, low chroma, professional)
+- Atmospheric photo with strong color grade (single-tone graded for brand mood)
+- Duotone treated image (two-color photo treatment, palette-locked)
+- Soft radial vignette + product crop (luxury / editorial feel)
+- Micro-noise gradient over solid (premium tactile depth, not flashy)
+- Color-blocked diptych (two flat fields meeting, modernist)
+
+### CTA Variation
+Pick the CTA style that fits each section, not a default pill every time:
+- Classic primary pill
+- Outline / ghost
+- Underlined inline link with arrow
+- Banner-style full-width CTA
+- Oversized headline + tiny CTA hint
+- CTA as caption under a strong visual
+
+Across the site, vary CTA style at least once. The page's primary action stays unmistakable.
+
+### Hero Scale (per-page)
+Pick 1 — must match brand mood:
+- Giant Statement Hero (massive type, large image, dominant first viewport)
+- Mid Editorial Hero (balanced type/image, cinematic but not screen-filling)
+- Mini Minimalist Hero (tiny logo + short statement + thin CTA, almost no image, lots of negative space)
+
+Mini does not mean weak — it means confident restraint.
+
+### Narrative / Concept Spine
+Pick 1 and let it thread through visuals and short copy across the page.
+- Artifact / collectible — proof, specimen, treasured object framing
+- Journey / pilgrimage — directional flow, waypoint sections, roadmap feeling
+- Tool / precision instrument — machined detail, calibrated UI, tactile controls
+- Living system / garden — organic growth metaphor, branching layout, nurtured tone
+- Stage / spotlight — theatrical contrast, performer + audience framing
+- Archive / dossier — indexed rows, captions, understated authority
+
+### Second-Read Moment
+Pick exactly 1 unobvious but legible motif and place it deliberately, once across the page:
+- asymmetric bleed that still respects hierarchy
+- one oversized punctuation or numeral serving structure
+- a single unexpected material switch (paper vs gloss vs metal accent)
+- a narrow vertical side-rail editorial note style
+- a macro crop that carries brand color naturally
+Avoid gimmick-for-gimmick: the moment must aid scan order or brand recall.
+
+Important:
+These are not coding instructions.
+They are visual-direction cues the generated design should imply.
+
+---
+
+## 3. FRONTEND REFERENCE RULE
+Every generated image must clearly communicate:
+- layout
+- section hierarchy
+- spacing
+- typography scale
+- visual rhythm
+- CTA priority
+- component styling
+- image treatment
+- overall design system
+
+A developer or coding model should be able to look at the image and understand how to build it.
+
+Do not produce vague abstract artwork when the request is for frontend.
+
+---
+
+## 4. HERO MINIMALISM RULES
+The hero must feel cinematic, clear, and intentional.
+
+### Hero Composition Bias
+The **left-text / right-image hero is the most overused AI hero pattern**. It is allowed, but it should not be your default starting point.
+
+Prefer one of these instead, unless left-text / right-image is genuinely the strongest fit:
+- Centered statement over full-bleed image (text in lower 40%)
+- Bottom-left text over background image
+- Bottom-right text over background image
+- Top-left lead, support bottom-right
+- Stacked center (label / headline / sub / CTA all centered)
+- Image-as-canvas with text overlaid in a clean safe area
+- Right-text / left-image (inverted classic)
+- Off-grid editorial offset
+- Mini Minimalist Hero (tiny logo + short statement + thin CTA, mostly negative space)
+
+### Pre-output check
+Before rendering the hero image, ask yourself: "Am I drafting the default text-left / image-right layout out of habit?" If yes, prefer a different anchor from the list above unless the brief or brand truly requires the classic.
+
+### Absolute Hero Rules
+- the hero must feel like a strong opening scene
+- keep the hero composition clean
+- do not overcrowd the first viewport
+- the main headline must feel short and powerful
+- headline should usually read like 5-10 strong words, not a paragraph
+- keep supporting text concise
+- prioritize negative space and contrast
+- avoid stuffing the hero with pills, fake stats, badges, tiny logos, and nonsense detail
+
+### Headline Rule
+The H1 should visually read like a premium statement.
+Do not let it feel long, weak, or overly wrapped.
+
+### Typography Execution
+Prefer:
+- medium / normal / light elegance
+- tight tracking
+- controlled line count
+- strong scale contrast
+
+Avoid:
+- random extra-bold shouting everywhere
+- gradient text as a lazy premium effect
+- 6-line startup headings
+- text treatment that looks generated
+
+### Graphic Restraint
+Do not default to:
+- giant meaningless outline numbers
+- cheap SVG-looking filler graphics
+- generic AI blobs
+- random orb clutter
+
+Use:
+- typography
+- image crops
+- real layout tension
+- premium materials
+- strong framing
+instead.
+
+---
+
+## 5. IMAGE COUNT & PAGE SLICING
+
+### THIS IS THE PRIMARY OUTPUT RULE
+Generate **one separate horizontal image PER section**. Always.
+
+- never combine multiple sections in a single image
+- never return a single tall slice that contains the whole page
+- never return one "best" image and skip the rest
+- never replace several sections with one collage
+
+If the request is ambiguous about section count, **default high**:
+- "hero" -> 1 image
+- "landing page" / "site template" -> default to 6 sections -> 6 images
+- "full website" -> default to 8 sections -> 8 images
+- "marketing site" -> default to 8 sections -> 8 images
+- "product page" -> default to 6 sections -> 6 images
+- "portfolio" -> default to 6 sections -> 6 images
+
+If the model can only render one image per call, generate them **sequentially in the same response**, one after the other, labeled "Section X of N: <name>" until the full set is delivered.
+
+### Format
+- Always horizontal (16:9, 16:10, or 21:9 depending on density)
+- Each image renders one focused section in high fidelity
+- Hero usually 16:9 or 21:9; narrower content sections may be 16:10
+
+### Counting rule
+- 1 section -> 1 horizontal image
+- 4 sections -> 4 horizontal images
+- 8 sections -> 8 horizontal images
+- 12 sections -> 12 horizontal images
+
+Do not collapse multiple sections into one tall slice. Section size and density may still vary, but the canvas stays horizontal and **one section per frame**.
+
+### Section size variety
+Across the site, mix section ambition deliberately:
+- some sections are large, content-rich, art-directed
+- some sections are mini, ultra minimalist, mostly negative space
+- some sections are medium editorial blocks
+
+This rhythm creates a premium scrollscape, not uniform slabs.
+
+### Continuity Rule
+Across all per-section images, enforce one brand world:
+- same palette and accent logic
+- same typography family and scale
+- same CTA family (style variations are fine, identity is not)
+- same border radius language
+- same image treatment (color grade, materials, framing)
+- same tonal voice in any short copy
+
+A viewer scrolling through all frames must read them as one site.
+
+---
+
+## 6. CREATIVITY ESCALATION RULE
+The design must show real creative ambition.
+
+Do not settle for the first obvious layout solution.
+Push the work beyond generic SaaS patterns.
+
+Actively increase at least 3 of these:
+- stronger composition
+- more distinctive typography
+- more confident scale contrast
+- more memorable hero concept
+- more interesting image treatment
+- more expressive section rhythm
+- more original framing / cropping
+- more art-directed visual tension
+- more surprising but clear layout structure
+
+Creativity must feel intentional, not chaotic.
+
+Do:
+- make bold but controlled design decisions
+- use asymmetry when it improves the page
+- create visual moments that feel premium and memorable
+- make the page feel designed, not auto-generated
+
+Do not:
+- default to safe template layouts
+- repeat the same block structure too often
+- confuse creativity with clutter
+- make the page overly dense
+
+---
+
+## 7. IMAGE-FIRST ART DIRECTION
+This skill must actively use images.
+
+Images are not optional decoration.
+Images are a core part of the frontend design language.
+
+Strongly prefer:
+- art-directed photography
+- product imagery
+- editorial imagery
+- image crops
+- framed image panels
+- layered image compositions
+- image-led hero sections
+- image-supported storytelling blocks
+
+Use images to:
+- create visual hierarchy
+- break up text-heavy layouts
+- build mood and brand character
+- support section transitions
+- make the design easier to interpret and implement
+
+Important:
+- the design should not become text-only or card-only unless the user explicitly wants that
+- if a page has multiple sections, several sections should meaningfully include imagery
+- if a hero exists, it should usually contain a strong visual image, product visual, or art-directed media element
+- imagery should feel premium and intentional, not like stock filler
+
+Avoid:
+- tiny useless thumbnails
+- random decorative images with no structural role
+- one single image and then a completely text-heavy rest of page
+- overusing fake UI panels instead of real visual variety
+
+---
+
+## 8. ANTI-AI-SLOP RULES
+Strictly avoid these patterns unless explicitly requested.
+
+### Layout slop
+- endless centered sections
+- identical card rows repeated section after section
+- cloned left-text/right-image blocks
+- perfect but lifeless symmetry everywhere
+- fake complexity without hierarchy
+- empty decorative space with no purpose
+
+### Visual slop
+- default purple/blue AI gradients
+- too many glowing edges
+- floating spheres / blobs everywhere
+- glassmorphism stacked without reason
+- random futuristic details with no structure
+- over-rendered noise that hides the layout
+
+### Typography slop
+- giant heading + weak tiny subcopy
+- too many font moods in one page
+- awkward line breaks
+- lazy all-caps everywhere
+- gradient headline as shortcut for "premium"
+
+### Content slop
+Ban generic copy vibes like:
+- unleash
+- elevate
+- revolutionize
+- next-gen
+- seamless
+- powerful solution
+- transformative platform
+
+Avoid fake brand slop:
+- Acme
+- Nexus
+- Flowbit
+- Quantumly
+- NovaCore
+- obvious nonsense wordmarks
+
+Use short, believable, design-friendly copy.
+
+### Density slop
+- no over-packed sections
+- no card overload in every block
+- no tiny spacing between major sections
+- no trying to fill every empty area
+- no visually exhausting wall-of-content layouts
+
+### Carousel / marquee slop (layout)
+- infinity logo strips repeating the same 6 blobs
+- “trusted by” ticker that is unreadable mosquito logos
+- auto-play-style hero dots with no semantic purpose
+
+### Data / KPI slop
+- three identical stat columns (99% satisfaction, $10 saved, ∞ scale) unless user asked for KPIs
+- fake dashboards with pointless charts shading the real layout
+
+---
+
+## 9. TYPOGRAPHY-FIRST DISCIPLINE
+Typography is not filler.
+Typography is a primary design material.
+
+Always ensure:
+- clear size contrast
+- obvious reading order
+- strong display moments
+- supporting text that is readable and brief
+- labels, captions, and section headings that reinforce structure
+
+For editorial directions:
+- let typography shape composition
+
+For tech/product directions:
+- let typography communicate trust and precision
+
+---
+
+## 10. SECTION RHYTHM RULE
+A high-end site does not feel like repeated boxes.
+
+Vary section rhythm across the page by changing:
+- density
+- image-to-text ratio
+- alignment
+- scale
+- whitespace
+- card grouping
+- background intensity
+- visual tempo
+
+Do not let every section feel generated from the same template.
+
+Important:
+- rhythm variation should not break overall cleanliness
+- keep the page visually balanced from top to bottom
+- section heights may vary, but the spacing between sections should feel controlled and fairly even
+- avoid abrupt jumps between very small and very large sections without enough breathing room
+- the full page should feel curated, smooth, and consistent
+
+---
+
+## 11. COMPONENT EXECUTION GUIDELINES
+
+### Diagonal Staggered Square Masonry
+Use square image or content blocks with strong staggered vertical rhythm.
+Should feel curated and graphic, not messy.
+
+### 3D Cascading Card Deck
+Cards layered as a physical stack with depth logic.
+Should feel premium and tactile, not gimmicky.
+
+### Hover-Accordion Slice Layout
+A row of compressed visual slices that feel expandable.
+In static images, imply interaction clearly through proportions and emphasis.
+
+### Pristine Gapless Bento Grid
+Mathematically clean grid.
+No accidental gaps.
+Mix large visual blocks with smaller dense information panels.
+
+### Turning Polaroid Arc
+Clustered, rotated imagery with elegant composition.
+Should feel styled and intentional, not scrapbook-random.
+
+### Off-Grid Editorial Layout
+Use asymmetry and tension with control.
+Must remain readable and clearly structured.
+
+### Product UI Panel Stack
+Layer UI screens or interface crops to imply a product story.
+Avoid generic fake dashboards.
+
+### Vertical Rhythm Lines
+Use fine lines and spacing systems to reinforce order and elegance.
+Never let them become decorative clutter.
+
+---
+
+## 12. DENSITY & SPACING DISCIPLINE
+Do not make everything too dense.
+
+The page should breathe.
+Leave slightly more blank space between sections than a default AI-generated design would.
+
+Rules:
+- use more even vertical spacing between major sections
+- keep section-to-section spacing consistent unless there is a strong design reason not to
+- avoid one section feeling very cramped while the next feels too empty
+- prefer a clean, balanced cadence across the page
+- allow negative space to create rhythm and emphasis
+- separate denser sections with calmer sections
+- avoid stacking too many cards, labels, and content blocks too tightly
+- smaller sections should still receive enough surrounding space so the page feels polished and intentional
+
+A premium page should feel:
+- open
+- composed
+- balanced
+- confident
+- breathable
+
+Not:
+- cramped
+- noisy
+- uneven
+- overfilled
+- visually exhausted
+
+Section rhythm should alternate with control:
+- some sections can be more content-rich
+- some sections can be smaller and calmer
+- but the overall spacing cadence should still feel even, clean, and deliberate
+
+Whitespace is a design tool.
+Use it deliberately.
+Do not let spacing become random.
+
+---
+
+## 13. COLOR & MATERIAL RULES
+
+### Palette Discipline
+Use one controlled palette across the entire site:
+- 1 primary (brand anchor)
+- 1 secondary (supporting tone)
+- 1 accent (used sparingly for CTA / highlight)
+- a neutral scale (background, surface, text, hairline)
+
+Section-level mood shifts must reuse the same palette — no full theme swap per section.
+
+### Background-image harmony
+When using full-bleed image backgrounds:
+- the image must tonally match the palette (not fight it)
+- use overlays (dark, light, or color tint) to keep text fully readable
+- the brand accent stays consistent regardless of background image
+
+### Gradient Discipline
+Gradients are **allowed and encouraged** when professional and subtle. They are not the same as AI slop gradients.
+
+Allowed (use confidently):
+- low-chroma palette-matched tonal gradients (e.g. ink to graphite, cream to sand, ivory to warm grey)
+- single-hue atmospheric grades behind hero photography
+- soft vignettes and radial depth that direct the eye
+- noise-textured gradients adding tactile depth without color noise
+- editorial color washes that match brand mood
+
+Banned (AI gradient slop):
+- rainbow / mesh blob gradients
+- purple-to-blue "AI" defaults
+- pink-to-orange "creator" defaults
+- neon edges and glow halos with no purpose
+- gradient text as a shortcut for "premium"
+- gradients that compete with imagery instead of supporting it
+
+### Background Confidence Rule
+Do not retreat to plain white surfaces by default. When the brief, brand mood, or section job calls for atmosphere, use:
+- a full-bleed image,
+- a duotone or graded photo,
+- a tonal gradient,
+- a tactile material,
+or a confident flat color field — picked deliberately, not as decoration.
+
+### Strong guidance
+- avoid rainbow randomness
+- avoid over-neon unless requested
+- keep contrast intentional
+- match accent colors to the chosen theme paradigm
+- gradients must always read as professional and intentional, never as visual noise
+
+### Materiality
+Where appropriate, add:
+- paper feel
+- glass feel
+- brushed metal feel
+- soft blur depth
+- tactile matte surfaces
+- editorial photo treatment
+
+But always keep the frontend structure readable.
+
+---
+
+## 14. IMAGE / MEDIA DIRECTION
+If imagery is present, it must support the layout.
+
+Allowed:
+- art-directed product visuals
+- refined editorial photography
+- UI crops
+- abstract forms with structural purpose
+- framed objects
+- premium texture use
+- campaign-style visuals
+
+Avoid:
+- irrelevant scenery
+- stock-photo cliches
+- decorative junk
+- visuals that overpower the page hierarchy
+
+---
+
+## 15. DEFAULT SITE PACKS
+
+### 4-section pack
+1. Hero
+2. Features
+3. Social proof / testimonial
+4. CTA
+
+### 8-section pack
+1. Hero
+2. Trust bar
+3. Features
+4. Product showcase
+5. Benefits / use cases
+6. Testimonials
+7. Pricing
+8. CTA
+
+### 12-section pack
+1. Hero
+2. Trust bar
+3. Feature grid
+4. Product preview
+5. Problem / solution
+6. Benefits
+7. Workflow
+8. Metrics / proof / integration
+9. Testimonials
+10. Pricing
+11. FAQ
+12. CTA + footer
+
+---
+
+## 16. MULTI-IMAGE CONSISTENCY RULE
+Because every section is its own image, consistency is critical. Across all per-section frames enforce:
+- same brand world
+- same type scale logic
+- same spacing discipline
+- same CTA family (style variations are fine, identity is not)
+- same icon or illustration mood
+- same image treatment (grade, framing, material vocabulary)
+- same tonal language in any copy
+
+Variation IS allowed in:
+- composition anchor (per section)
+- background mode (per section)
+- section size and density
+- which "second-read" moment appears
+
+A viewer flipping through every per-section frame must still recognize one brand. Anything that breaks brand recall is over-variation.
+
+---
+
+## 17. CLARITY CHECK
+Before finalizing, verify internally:
+
+1. Is the hierarchy obvious?
+2. Is the hero clean enough?
+3. Is the design visually distinctive?
+4. Is it free of obvious AI tells?
+5. Is it premium rather than template-like?
+6. Can someone code from this?
+7. If multiple images exist, do they clearly belong together?
+8. Is imagery used strongly enough (with variation, not one repeated crop)?
+9. Does the page breathe, or is it too dense?
+10. Is there enough spacing between sections?
+11. Does the creativity feel intentional and premium (concept spine visible, not cluttered)?
+12. Is the spacing between sections even and controlled?
+13. Do smaller sections still have enough surrounding space to feel clean?
+14. Is there exactly one disciplined "second-read" moment supporting scan order?
+15. Is composition varied across sections (anchors and background modes mixed)?
+16. Is the hero scale (giant / mid / mini) chosen and executed cleanly?
+17. Is there a clear conversion path (hook -> proof -> action) even in artistic sites?
+18. Is the palette consistent across all per-section images?
+19. Is each image horizontal and one-section-only?
+20. Is the **total number of images equal to the number of sections** (never fewer)?
+21. Is the hero using a varied composition (not defaulting to left-text / right-image out of habit)?
+
+If not, refine internally before output. If the count is wrong, regenerate the missing sections. If the hero feels like a reflexive left-text / right-image default, prefer a different composition anchor.
+
+---
+
+## 18. EXTRA CREATIVITY & IMPLEMENTATION EDGE
+
+Apply unless the user opts out:
+
+### Cross-section contrast
+Across the slice, deliberately vary foreground/background intensity at least twice (lighter → richer → calmer) so the scroll feels paced, not monotonous slabs.
+
+### CTA specificity
+Prefer one unmistakable primary action per major viewport tier; secondary actions must look secondary (scale, outline, ghost), not clones of primary.
+
+### Image variety inside one comp
+Mix at least **two distinct image crops** where multiple sections exist — e.g. macro product + contextual environment, or portrait editorial + widescreen artifact — avoiding one repeated stock silhouette.
+
+### Data-viz restraint
+Charts, sparklines, and graphs appear only when the site type logically needs them (analytics, pricing, infra, observability brands). Else keep proof human (quotes, receipts, timelines, screenshots of real workflows).
+
+### Cultural / tonal alignment
+When the brief names an industry or region, steer palette and typographic temperament to match — don’t ship default “neutral SF startup” unless the brief is intentionally generic SaaS.
+
+### Mobile-implied fidelity (even for desktop mocks)
+Maintain tap-friendly hit sizes and readable caption sizes visually; stacking order should imply a sane single-column narrative.
+
+### Conversion focus
+Each section has a job. Even when the design is artistic, the page must read as a real product or brand site:
+- the hero communicates value in seconds and offers one obvious next action
+- proof sections (logos, quotes, metrics) feel earned, not stuffed
+- pricing or CTA sections feel decisive, not buried
+- the final section closes: a single strong CTA + supporting trust cue
+Avoid pure mood reels with no funnel logic.
+
+### Composition variety check
+Across all per-section images, internally log the chosen composition anchor and background mode. Reject the set if:
+- the same composition anchor repeats more than 2 sections in a row
+- the same background mode repeats more than 3 sections in a row
+- every section is inline-asset (no full-bleed background ever appears) **AND** the brief does not call for minimalism / typography-only / swiss / ultra simple
+
+For non-minimalist briefs: push for at least one full-bleed (or duotone / atmospheric) background and at least one mini minimalist section in any multi-section site.
+
+For minimalist briefs: this rule is suspended. Restraint is the design.
+
+---
+
+## 19. RESPONSE BEHAVIOR
+When the user asks for a frontend design:
+1. infer site type and primary conversion goal
+2. infer number of sections (if unclear, use the defaults from §5: landing page = 6, full website = 8)
+3. **commit out loud** to the section count and announce it ("Generating N horizontal images, one per section")
+4. plan ONE horizontal image PER SECTION — always separate generations, never collapse
+5. choose Hero Scale for the whole site (giant / mid / mini)
+5. choose a strong visual combination (theme, type, hero arch, section system, motion, narrative spine, second-read moment)
+7. for each section: pick a Composition Anchor, Background Mode, and CTA Variation — vary across sections
+8. choose 4 signature components used appropriately across sections
+9. enforce hero minimalism + section size variety (some giant, some mini)
+10. enforce strong image usage including full-bleed backgrounds where it fits
+11. lock one consistent palette across all images
+12. apply §18 EXTRA CREATIVITY & IMPLEMENTATION EDGE
+13. keep spacing generous, even, and clean
+14. remove AI slop (including marquee / fake KPI clichés unless requested)
+15. run §17 CLARITY CHECK
+16. **generate every per-section horizontal image, labeled "Section X of N: <name>"**, until the full set is delivered. Do not stop early. Do not summarize. Do not return only one image.
+
+Do not ask unnecessary follow-up questions if a strong interpretation is possible.
+
+---
+
+## 20. EXAMPLE INTERPRETATIONS
+
+### Example 1
+User: "make a hero section for an AI startup"
+
+Interpretation:
+- 1 horizontal image
+- Hero Scale: Mid Editorial or Giant Statement
+- Composition Anchor: bottom-left text over full-bleed product/atmosphere image
+- Background Mode: full-bleed image with dark tonal overlay
+- CTA Variation: outlined inline + small label hint
+- Palette: Deep Dark or Bold Studio Solid, one consistent accent
+- no cliche dashboard spam, no purple AI glow
+
+### Example 2
+User: "design 8 sections for a fintech website"
+
+Interpretation:
+- 8 separate horizontal images (one per section)
+- Hero Scale: Mid Editorial (trust-driven)
+- vary Composition Anchor across sections (centered low, right-third caption, bottom-left over chart visual, stacked center for closing CTA)
+- Background Mode mix: solid surface, full-bleed image background once, editorial side-image at use cases
+- one consistent palette (e.g. ink + paper + single brand accent)
+- conversion path: hook -> proof bar -> features -> use case -> testimonial -> pricing -> FAQ -> final CTA
+
+### Example 3
+User: "creative agency landing page, 12 sections"
+
+Interpretation:
+- 12 horizontal images (one per section)
+- Hero Scale: Giant Statement OR Mini Minimalist (decisive choice, not in-between)
+- editorial / poster-like direction; off-grid composition appears 2-3 times
+- multiple Background Modes (full-bleed image at hero + showcase, editorial side-image at case studies, solid + accent for process)
+- palette consistent throughout, with one bold accent recurring
+- closing CTA section: mini minimalist, strong type, single primary action
+
+---
+
+## 21. FINAL GOAL
+Generate frontend reference images that feel:
+- artistic
+- premium
+- clear
+- structured
+- image-led
+- breathable
+- memorable
+- anti-generic
+- implementation-friendly
+
+The result should look like a top-tier website concept with strong imagery, confident creativity, and generous spacing - not a dense, repetitive AI layout.

.claude/skills/industrial-brutalist-ui/SKILL.md

@@ -0,0 +1,92 @@
+---
+name: industrial-brutalist-ui
+description: Raw mechanical interfaces fusing Swiss typographic print with military terminal aesthetics. Rigid grids, extreme type scale contrast, utilitarian color, analog degradation effects. For data-heavy dashboards, portfolios, or editorial sites that need to feel like declassified blueprints.
+---
+
+# SKILL: Industrial Brutalism & Tactical Telemetry UI
+
+## 1. Skill Meta
+**Name:** Industrial Brutalism & Tactical Telemetry Interface Engineering
+**Description:** Advanced proficiency in architecting web interfaces that synthesize mid-century Swiss Typographic design, industrial manufacturing manuals, and retro-futuristic aerospace/military terminal interfaces. This discipline requires absolute mastery over rigid modular grids, extreme typographic scale contrast, purely utilitarian color palettes, and the programmatic simulation of analog degradation (halftones, CRT scanlines, bitmap dithering). The objective is to construct digital environments that project raw functionality, mechanical precision, and high data density, deliberately discarding conventional consumer UI patterns.
+
+## 2. Visual Archetypes
+The design system operates by merging two distinct but highly compatible visual paradigms. **Pick ONE per project and commit to it. Do not alternate or mix both modes within the same interface.**
+
+### 2.1 Swiss Industrial Print
+Derived from 1960s corporate identity systems and heavy machinery blueprints.
+*   **Characteristics:** High-contrast light modes (newsprint/off-white substrates). Reliance on monolithic, heavy sans-serif typography. Unforgiving structural grids outlined by visible dividing lines. Aggressive, asymmetric use of negative space punctuated by oversized, viewport-bleeding numerals or letterforms. Heavy use of primary red as an alert/accent color.
+
+### 2.2 Tactical Telemetry & CRT Terminal
+Derived from classified military databases, legacy mainframes, and aerospace Heads-Up Displays (HUDs).
+*   **Characteristics:** Dark mode exclusivity. High-density tabular data presentation. Absolute dominance of monospaced typography. Integration of technical framing devices (ASCII brackets, crosshairs). Application of simulated hardware limitations (phosphor glow, scanlines, low bit-depth rendering).
+
+## 3. Typographic Architecture
+Typography is the primary structural and decorative infrastructure. Imagery is secondary. The system demands extreme variance in scale, weight, and spacing.
+
+### 3.1 Macro-Typography (Structural Headers)
+*   **Classification:** Neo-Grotesque / Heavy Sans-Serif.
+*   **Optimal Web Fonts:** Neue Haas Grotesk (Black), Inter (Extra Bold/Black), Archivo Black, Roboto Flex (Heavy), Monument Extended.
+*   **Implementation Parameters:**
+    *   **Scale:** Deployed at massive scales using fluid typography (e.g., `clamp(4rem, 10vw, 15rem)`).
+    *   **Tracking (Letter-spacing):** Extremely tight, often negative (`-0.03em` to `-0.06em`), forcing glyphs to form solid architectural blocks.
+    *   **Leading (Line-height):** Highly compressed (`0.85` to `0.95`).
+    *   **Casing:** Exclusively uppercase for structural impact.
+
+### 3.2 Micro-Typography (Data & Telemetry)
+*   **Classification:** Monospace / Technical Sans.
+*   **Optimal Web Fonts:** JetBrains Mono, IBM Plex Mono, Space Mono, VT323, Courier Prime.
+*   **Implementation Parameters:**
+    *   **Scale:** Fixed and small (`10px` to `14px` / `0.7rem` to `0.875rem`).
+    *   **Tracking:** Generous (`0.05em` to `0.1em`) to simulate mechanical typewriter spacing or terminal matrices.
+    *   **Leading:** Standard to tight (`1.2` to `1.4`).
+    *   **Casing:** Exclusively uppercase. Used for all metadata, navigation, unit IDs, and coordinates.
+
+### 3.3 Textural Contrast (Artistic Disruption)
+*   **Classification:** High-Contrast Serif.
+*   **Optimal Web Fonts:** Playfair Display, EB Garamond, Times New Roman.
+*   **Implementation Parameters:** Used exceedingly sparingly. Must be subjected to heavy post-processing (halftone filters, 1-bit dithering) to degrade vector perfection and create textural juxtaposition against the clean sans-serifs.
+
+## 4. Color System
+The color architecture is uncompromising. Gradients, soft drop shadows, and modern translucency are strictly prohibited. Colors simulate physical media or primitive emissive displays.
+
+**CRITICAL: Choose ONE substrate palette per project and use it consistently. Never mix light and dark substrates within the same interface.**
+
+### If Swiss Industrial Print (Light):
+*   **Background:** `#F4F4F0` or `#EAE8E3` (Matte, unbleached documentation paper).
+*   **Foreground:** `#050505` to `#111111` (Carbon Ink).
+*   **Accent:** `#E61919` or `#FF2A2A` (Aviation/Hazard Red). This is the ONLY accent color. Used for strike-throughs, thick structural dividing lines, or vital data highlights.
+
+### If Tactical Telemetry (Dark):
+*   **Background:** `#0A0A0A` or `#121212` (Deactivated CRT. Avoid pure `#000000`).
+*   **Foreground:** `#EAEAEA` (White phosphor). This is the primary text color.
+*   **Accent:** `#E61919` or `#FF2A2A` (Aviation/Hazard Red). Same red, same rules.
+*   **Terminal Green (`#4AF626`):** Optional. Use ONLY for a single specific UI element (e.g., one status indicator or one data readout) — never as a general text color. If it doesn't serve a clear purpose, omit it entirely.
+
+## 5. Layout and Spatial Engineering
+The layout must appear mathematically engineered. It rejects conventional web padding in favor of visible compartmentalization.
+
+*   **The Blueprint Grid:** Strict adherence to CSS Grid architectures. Elements do not float; they are anchored precisely to grid tracks and intersections.
+*   **Visible Compartmentalization:** Extensive utilization of solid borders (`1px` or `2px solid`) to delineate distinct zones of information. Horizontal rules (`<hr>`) frequently span the entire container width to segregate operational units.
+*   **Bimodal Density:** Layouts oscillate between extreme data density (tightly packed monospace metadata clustered together) and vast expanses of calculated negative space framing macro-typography.
+*   **Geometry:** Absolute rejection of `border-radius`. All corners must be exactly 90 degrees to enforce mechanical rigidity.
+
+## 6. UI Components and Symbology
+Standard web UI conventions are replaced with utilitarian, industrial graphic elements.
+
+*   **Syntax Decoration:** Utilization of ASCII characters to frame data points.
+    *   *Framing:* `[ DELIVERY SYSTEMS ]`, `< RE-IND >`
+    *   *Directional:* `>>>`, `///`, `\\\\`
+*   **Industrial Markers:** Prominent integration of registration (`®`), copyright (`©`), and trademark (`™`) symbols functioning as structural geometric elements rather than legal text.
+*   **Technical Assets:** Integration of crosshairs (`+`) at grid intersections, repeating vertical lines (barcodes), thick horizontal warning stripes, and randomized string data (e.g., `REV 2.6`, `UNIT / D-01`) to simulate active mechanical processes.
+
+## 7. Textural and Post-Processing Effects
+To prevent the design from appearing purely digital, simulated analog degradation is engineered into the frontend via CSS and SVG filters.
+
+*   **Halftone and 1-Bit Dithering:** Transforming continuous-tone images or large serif typography into dot-matrix patterns. Achieved via pre-processing or CSS `mix-blend-mode: multiply` overlays combined with SVG radial dot patterns.
+*   **CRT Scanlines:** For terminal interfaces, applying a `repeating-linear-gradient` to the background to simulate horizontal electron beam sweeps (e.g., `repeating-linear-gradient(0deg, transparent, transparent 2px, rgba(0,0,0,0.1) 2px, rgba(0,0,0,0.1) 4px)`).
+*   **Mechanical Noise:** A global, low-opacity SVG static/noise filter applied to the DOM root to introduce a unified physical grain across both dark and light modes.
+
+## 8. Web Engineering Directives
+1.  **Grid Determinism:** Utilize `display: grid; gap: 1px;` with contrasting parent/child background colors to generate mathematically perfect, razor-thin dividing lines without complex border declarations.
+2.  **Semantic Rigidity:** Construct the DOM using precise semantic tags (`<data>`, `<samp>`, `<kbd>`, `<output>`, `<dl>`) to accurately reflect the technical nature of the telemetry.
+3.  **Typography Clamping:** Implement CSS `clamp()` functions exclusively for macro-typography to ensure massive text scales aggressively while maintaining structural integrity across viewports.

.claude/skills/minimalist-ui/SKILL.md

@@ -0,0 +1,85 @@
+---
+name: minimalist-ui
+description: Clean editorial-style interfaces. Warm monochrome palette, typographic contrast, flat bento grids, muted pastels. No gradients, no heavy shadows.
+---
+
+# Protocol: Premium Utilitarian Minimalism UI Architect
+
+## 1. Protocol Overview
+Name: Premium Utilitarian Minimalism & Editorial UI
+Description: An advanced frontend engineering directive for generating highly refined, ultra-minimalist, "document-style" web interfaces analogous to top-tier workspace platforms. This protocol strictly enforces a high-contrast warm monochrome palette, bespoke typographic hierarchies, meticulous structural macro-whitespace, bento-grid layouts, and an ultra-flat component architecture with deliberate muted pastel accents. It actively rejects standard generic SaaS design trends.
+
+## 2. Absolute Negative Constraints (Banned Elements)
+The AI must strictly avoid the following generic web development defaults:
+- DO NOT use the "Inter", "Roboto", or "Open Sans" typefaces.
+- DO NOT use generic, thin-line icon libraries like "Lucide", "Feather", or standard "Heroicons".
+- DO NOT use Tailwind's default heavy drop shadows (e.g., `shadow-md`, `shadow-lg`, `shadow-xl`). Shadows must be practically non-existent or heavily customized to be ultra-diffuse and low opacity (< 0.05).
+- DO NOT use primary colored backgrounds for large elements or sections (e.g., no bright blue, green, or red hero sections).
+- DO NOT use gradients, neon colors, or 3D glassmorphism (beyond subtle navbar blurs).
+- DO NOT use `rounded-full` (pill shapes) for large containers, cards, or primary buttons.
+- DO NOT use emojis anywhere in code, markup, text content, headings, or alt text. Replace with proper icons or clean SVG primitives.
+- DO NOT use generic placeholder names like "John Doe", "Acme Corp", or "Lorem Ipsum". Use realistic, contextual content.
+- DO NOT use AI copywriting clichés: "Elevate", "Seamless", "Unleash", "Next-Gen", "Game-changer", "Delve". Write plain, specific language.
+
+## 3. Typographic Architecture
+The interface must rely on extreme typographic contrast and premium font selection to establish an editorial feel.
+- Primary Sans-Serif (Body, UI, Buttons): Use clean, geometric, or system-native fonts with character. Target: `font-family: 'SF Pro Display', 'Geist Sans', 'Helvetica Neue', 'Switzer', sans-serif`.
+- Editorial Serif (Hero Headings & Quotes): Target: `font-family: 'Lyon Text', 'Newsreader', 'Playfair Display', 'Instrument Serif', serif`. Apply tight tracking (`letter-spacing: -0.02em` to `-0.04em`) and tight line-height (`1.1`).
+- Monospace (Code, Keystrokes, Meta-data): Target: `font-family: 'Geist Mono', 'SF Mono', 'JetBrains Mono', monospace`.
+- Text Colors: Body text must never be absolute black (`#000000`). Use off-black/charcoal (`#111111` or `#2F3437`) with a generous `line-height` of `1.6` for legibility. Secondary text should be muted gray (`#787774`).
+
+## 4. Color Palette (Warm Monochrome + Spot Pastels)
+Color is a scarce resource, utilized only for semantic meaning or subtle accents.
+- Canvas / Background: Pure White `#FFFFFF` or Warm Bone/Off-White `#F7F6F3` / `#FBFBFA`.
+- Primary Surface (Cards): `#FFFFFF` or `#F9F9F8`.
+- Structural Borders / Dividers: Ultra-light gray `#EAEAEA` or `rgba(0,0,0,0.06)`.
+- Accent Colors: Exclusively use highly desaturated, washed-out pastels for tags, inline code backgrounds, or subtle icon backgrounds.
+  - Pale Red: `#FDEBEC` (Text: `#9F2F2D`)
+  - Pale Blue: `#E1F3FE` (Text: `#1F6C9F`)
+  - Pale Green: `#EDF3EC` (Text: `#346538`)
+  - Pale Yellow: `#FBF3DB` (Text: `#956400`)
+
+## 5. Component Specifications
+- Bento Box Feature Grids:
+  - Utilize asymmetrical CSS Grid layouts.
+  - Cards must have exactly `border: 1px solid #EAEAEA`.
+  - Border-radius must be crisp: `8px` or `12px` maximum.
+  - Internal padding must be generous (e.g., `24px` to `40px`).
+- Primary Call-To-Action (Buttons):
+  - Solid background `#111111`, text `#FFFFFF`. 
+  - Slight border-radius (`4px` to `6px`). No box-shadow. 
+  - Hover state should be a subtle color shift to `#333333` or a micro-scale `transform: scale(0.98)`.
+- Tags & Status Badges:
+  - Pill-shaped (`border-radius: 9999px`), very small typography (`text-xs`), uppercase with wide tracking (`letter-spacing: 0.05em`).
+  - Background must use the defined Muted Pastels.
+- Accordions (FAQ):
+  - Strip all container boxes. Separate items only with a `border-bottom: 1px solid #EAEAEA`.
+  - Use a clean, sharp `+` and `-` icon for the toggle state.
+- Keystroke Micro-UIs:
+  - Render shortcuts as physical keys using `<kbd>` tags: `border: 1px solid #EAEAEA`, `border-radius: 4px`, `background: #F7F6F3`, using the Monospace font.
+- Faux-OS Window Chrome:
+  - When mocking up software, wrap it in a minimalist container with a white top bar containing three small, light gray circles (replicating macOS window controls).
+
+## 6. Iconography & Imagery Directives
+- System Icons: Use "Phosphor Icons (Bold or Fill weights)" or "Radix UI Icons" for a technical, slightly thicker-stroke aesthetic. Standardize stroke width across all icons.
+- Illustrations: Monochromatic, rough continuous-line ink sketches on a white background, featuring a single offset geometric shape filled with a muted pastel color.
+- Photography: Use high-quality, desaturated images with a warm tone. Apply subtle overlays (`opacity: 0.04` warm grain) to blend photos into the monochrome palette. Never use oversaturated stock photos. Use reliable placeholders like `https://picsum.photos/seed/{context}/1200/800` when real assets are unavailable.
+- Hero & Section Backgrounds: Sections should not feel empty and flat. Use subtle full-width background imagery at very low opacity, soft radial light spots (`radial-gradient` with warm tones at `opacity: 0.03`), or minimal geometric line patterns to add depth without breaking the clean aesthetic.
+
+## 7. Subtle Motion & Micro-Animations
+Motion should feel invisible — present but never distracting. The goal is quiet sophistication, not spectacle.
+- Scroll Entry: Elements fade in gently as they enter the viewport. Use `translateY(12px)` + `opacity: 0` resolving over `600ms` with `cubic-bezier(0.16, 1, 0.3, 1)`. Use `IntersectionObserver`, never `window.addEventListener('scroll')`.
+- Hover States: Cards lift with an ultra-subtle shadow shift (`box-shadow` transitioning from `0 0 0` to `0 2px 8px rgba(0,0,0,0.04)` over `200ms`). Buttons respond with `scale(0.98)` on `:active`.
+- Staggered Reveals: Lists and grid items enter with a cascade delay (`animation-delay: calc(var(--index) * 80ms)`). Never mount everything at once.
+- Background Ambient Motion: Optional. A single, very slow-moving radial gradient blob (`animation-duration: 20s+`, `opacity: 0.02-0.04`) drifting behind hero sections. Must be applied to a `position: fixed; pointer-events: none` layer. Never on scrolling containers.
+- Performance: Animate exclusively via `transform` and `opacity`. No layout-triggering properties (`top`, `left`, `width`, `height`). Use `will-change: transform` sparingly and only on actively animating elements.
+
+## 8. Execution Protocol
+When tasked with writing frontend code (HTML, React, Tailwind, Vue) or designing a layout:
+1. Establish the macro-whitespace first. Use massive vertical padding between sections (e.g., `py-24` or `py-32` in Tailwind).
+2. Constrain the main typography content width to `max-w-4xl` or `max-w-5xl`.
+3. Apply the custom typographic hierarchy and monochromatic color variables immediately.
+4. Ensure every card, divider, and border adheres strictly to the `1px solid #EAEAEA` rule.
+5. Add scroll-entry animations to all major content blocks.
+6. Ensure sections have visual depth through imagery, ambient gradients, or subtle textures — no empty flat backgrounds.
+7. Provide code that reflects this high-end, uncluttered, editorial aesthetic natively without requiring manual adjustments.

.claude/skills/redesign-existing-projects/SKILL.md

@@ -0,0 +1,178 @@
+---
+name: redesign-existing-projects
+description: Upgrades existing websites and apps to premium quality. Audits current design, identifies generic AI patterns, and applies high-end design standards without breaking functionality. Works with any CSS framework or vanilla CSS.
+---
+
+# Redesign Skill
+
+## How This Works
+
+When applied to an existing project, follow this sequence:
+
+1. **Scan** — Read the codebase. Identify the framework, styling method (Tailwind, vanilla CSS, styled-components, etc.), and current design patterns.
+2. **Diagnose** — Run through the audit below. List every generic pattern, weak point, and missing state you find.
+3. **Fix** — Apply targeted upgrades working with the existing stack. Do not rewrite from scratch. Improve what's there.
+
+## Design Audit
+
+### Typography
+
+Check for these problems and fix them:
+
+- **Browser default fonts or Inter everywhere.** Replace with a font that has character. Good options: `Geist`, `Outfit`, `Cabinet Grotesk`, `Satoshi`. For editorial/creative projects, pair a serif header with a sans-serif body.
+- **Headlines lack presence.** Increase size for display text, tighten letter-spacing, reduce line-height. Headlines should feel heavy and intentional.
+- **Body text too wide.** Limit paragraph width to roughly 65 characters. Increase line-height for readability.
+- **Only Regular (400) and Bold (700) weights used.** Introduce Medium (500) and SemiBold (600) for more subtle hierarchy.
+- **Numbers in proportional font.** Use a monospace font or enable tabular figures (`font-variant-numeric: tabular-nums`) for data-heavy interfaces.
+- **Missing letter-spacing adjustments.** Use negative tracking for large headers, positive tracking for small caps or labels.
+- **All-caps subheaders everywhere.** Try lowercase italics, sentence case, or small-caps instead.
+- **Orphaned words.** Single words sitting alone on the last line. Fix with `text-wrap: balance` or `text-wrap: pretty`.
+
+### Color and Surfaces
+
+- **Pure `#000000` background.** Replace with off-black, dark charcoal, or tinted dark (`#0a0a0a`, `#121212`, or a dark navy).
+- **Oversaturated accent colors.** Keep saturation below 80%. Desaturate accents so they blend with neutrals instead of screaming.
+- **More than one accent color.** Pick one. Remove the rest. Consistency beats variety.
+- **Mixing warm and cool grays.** Stick to one gray family. Tint all grays with a consistent hue (warm or cool, not both).
+- **Purple/blue "AI gradient" aesthetic.** This is the most common AI design fingerprint. Replace with neutral bases and a single, considered accent.
+- **Generic `box-shadow`.** Tint shadows to match the background hue. Use colored shadows (e.g., dark blue shadow on a blue background) instead of pure black at low opacity.
+- **Flat design with zero texture.** Add subtle noise, grain, or micro-patterns to backgrounds. Pure flat vectors feel sterile.
+- **Perfectly even gradients.** Break the uniformity with radial gradients, noise overlays, or mesh gradients instead of standard linear 45-degree fades.
+- **Inconsistent lighting direction.** Audit all shadows to ensure they suggest a single, consistent light source.
+- **Random dark sections in a light mode page (or vice versa).** A single dark-background section breaking an otherwise light page looks like a copy-paste accident. Either commit to a full dark mode or keep a consistent background tone throughout. If contrast is needed, use a slightly darker shade of the same palette — not a sudden jump to `#111` in the middle of a cream page.
+- **Empty, flat sections with no visual depth.** Sections that are just text on a plain background feel unfinished. Add high-quality background imagery (blurred, overlaid, or masked), subtle patterns, or ambient gradients. Use reliable placeholder sources like `https://picsum.photos/seed/{name}/1920/1080` when real assets are not available. Experiment with background images behind hero sections, feature blocks, or CTAs — even a subtle full-width photo at low opacity adds presence.
+
+### Layout
+
+- **Everything centered and symmetrical.** Break symmetry with offset margins, mixed aspect ratios, or left-aligned headers over centered content.
+- **Three equal card columns as feature row.** This is the most generic AI layout. Replace with a 2-column zig-zag, asymmetric grid, horizontal scroll, or masonry layout.
+- **Using `height: 100vh` for full-screen sections.** Replace with `min-height: 100dvh` to prevent layout jumping on mobile browsers (iOS Safari viewport bug).
+- **Complex flexbox percentage math.** Replace with CSS Grid for reliable multi-column structures.
+- **No max-width container.** Add a container constraint (around 1200-1440px) with auto margins so content doesn't stretch edge-to-edge on wide screens.
+- **Cards of equal height forced by flexbox.** Allow variable heights or use masonry when content varies in length.
+- **Uniform border-radius on everything.** Vary the radius: tighter on inner elements, softer on containers.
+- **No overlap or depth.** Elements sit flat next to each other. Use negative margins to create layering and visual depth.
+- **Symmetrical vertical padding.** Top and bottom padding are always identical. Adjust optically — bottom padding often needs to be slightly larger.
+- **Dashboard always has a left sidebar.** Try top navigation, a floating command menu, or a collapsible panel instead.
+- **Missing whitespace.** Double the spacing. Let the design breathe. Dense layouts work for data dashboards, not for marketing pages.
+- **Buttons not bottom-aligned in card groups.** When cards have different content lengths, CTAs end up at random heights. Pin buttons to the bottom of each card so they form a clean horizontal line regardless of content above.
+- **Feature lists starting at different vertical positions.** In pricing tables or comparison cards, the list of features should start at the same Y position across all columns. Use consistent spacing above the list or fixed-height title/price blocks.
+- **Inconsistent vertical rhythm in side-by-side elements.** When placing cards, columns, or panels next to each other, align shared elements (titles, descriptions, prices, buttons) across all items. Misaligned baselines make the layout look broken.
+- **Mathematical alignment that looks optically wrong.** Centering by the math doesn't always look centered to the eye. Icons next to text, play buttons in circles, or text in buttons often need 1-2px optical adjustments to feel right.
+
+### Interactivity and States
+
+- **No hover states on buttons.** Add background shift, slight scale, or translate on hover.
+- **No active/pressed feedback.** Add a subtle `scale(0.98)` or `translateY(1px)` on press to simulate a physical click.
+- **Instant transitions with zero duration.** Add smooth transitions (200-300ms) to all interactive elements.
+- **Missing focus ring.** Ensure visible focus indicators for keyboard navigation. This is an accessibility requirement, not optional.
+- **No loading states.** Replace generic circular spinners with skeleton loaders that match the layout shape.
+- **No empty states.** An empty dashboard showing nothing is a missed opportunity. Design a composed "getting started" view.
+- **No error states.** Add clear, inline error messages for forms. Do not use `window.alert()`.
+- **Dead links.** Buttons that link to `#`. Either link to real destinations or visually disable them.
+- **No indication of current page in navigation.** Style the active nav link differently so users know where they are.
+- **Scroll jumping.** Anchor clicks jump instantly. Add `scroll-behavior: smooth`.
+- **Animations using `top`, `left`, `width`, `height`.** Switch to `transform` and `opacity` for GPU-accelerated, smooth animation.
+
+### Content
+
+- **Generic names like "John Doe" or "Jane Smith".** Use diverse, realistic-sounding names.
+- **Fake round numbers like `99.99%`, `50%`, `$100.00`.** Use organic, messy data: `47.2%`, `$99.00`, `+1 (312) 847-1928`.
+- **Placeholder company names like "Acme Corp", "Nexus", "SmartFlow".** Invent contextual, believable brand names.
+- **AI copywriting cliches.** Never use "Elevate", "Seamless", "Unleash", "Next-Gen", "Game-changer", "Delve", "Tapestry", or "In the world of...". Write plain, specific language.
+- **Exclamation marks in success messages.** Remove them. Be confident, not loud.
+- **"Oops!" error messages.** Be direct: "Connection failed. Please try again."
+- **Passive voice.** Use active voice: "We couldn't save your changes" instead of "Mistakes were made."
+- **All blog post dates identical.** Randomize dates to appear real.
+- **Same avatar image for multiple users.** Use unique assets for every distinct person.
+- **Lorem Ipsum.** Never use placeholder latin text. Write real draft copy.
+- **Title Case On Every Header.** Use sentence case instead.
+
+### Component Patterns
+
+- **Generic card look (border + shadow + white background).** Remove the border, or use only background color, or use only spacing. Cards should exist only when elevation communicates hierarchy.
+- **Always one filled button + one ghost button.** Add text links or tertiary styles to reduce visual noise.
+- **Pill-shaped "New" and "Beta" badges.** Try square badges, flags, or plain text labels.
+- **Accordion FAQ sections.** Use a side-by-side list, searchable help, or inline progressive disclosure.
+- **3-card carousel testimonials with dots.** Replace with a masonry wall, embedded social posts, or a single rotating quote.
+- **Pricing table with 3 towers.** Highlight the recommended tier with color and emphasis, not just extra height.
+- **Modals for everything.** Use inline editing, slide-over panels, or expandable sections instead of popups for simple actions.
+- **Avatar circles exclusively.** Try squircles or rounded squares for a less generic look.
+- **Light/dark toggle always a sun/moon switch.** Use a dropdown, system preference detection, or integrate it into settings.
+- **Footer link farm with 4 columns.** Simplify. Focus on main navigational paths and legally required links.
+
+### Iconography
+
+- **Lucide or Feather icons exclusively.** These are the "default" AI icon choice. Use Phosphor, Heroicons, or a custom set for differentiation.
+- **Rocketship for "Launch", shield for "Security".** Replace cliche metaphors with less obvious icons (bolt, fingerprint, spark, vault).
+- **Inconsistent stroke widths across icons.** Audit all icons and standardize to one stroke weight.
+- **Missing favicon.** Always include a branded favicon.
+- **Stock "diverse team" photos.** Use real team photos, candid shots, or a consistent illustration style instead of uncanny stock imagery.
+
+### Code Quality
+
+- **Div soup.** Use semantic HTML: `<nav>`, `<main>`, `<article>`, `<aside>`, `<section>`.
+- **Inline styles mixed with CSS classes.** Move all styling to the project's styling system.
+- **Hardcoded pixel widths.** Use relative units (`%`, `rem`, `em`, `max-width`) for flexible layouts.
+- **Missing alt text on images.** Describe image content for screen readers. Never leave `alt=""` or `alt="image"` on meaningful images.
+- **Arbitrary z-index values like `9999`.** Establish a clean z-index scale in the theme/variables.
+- **Commented-out dead code.** Remove all debug artifacts before shipping.
+- **Import hallucinations.** Check that every import actually exists in `package.json` or the project dependencies.
+- **Missing meta tags.** Add proper `<title>`, `description`, `og:image`, and social sharing meta tags.
+
+### Strategic Omissions (What AI Typically Forgets)
+
+- **No legal links.** Add privacy policy and terms of service links in the footer.
+- **No "back" navigation.** Dead ends in user flows. Every page needs a way back.
+- **No custom 404 page.** Design a helpful, branded "page not found" experience.
+- **No form validation.** Add client-side validation for emails, required fields, and format checks.
+- **No "skip to content" link.** Essential for keyboard users. Add a hidden skip-link.
+- **No cookie consent.** If required by jurisdiction, add a compliant consent banner.
+
+## Upgrade Techniques
+
+When upgrading a project, pull from these high-impact techniques to replace generic patterns:
+
+### Typography Upgrades
+- **Variable font animation.** Interpolate weight or width on scroll or hover for text that feels alive.
+- **Outlined-to-fill transitions.** Text starts as a stroke outline and fills with color on scroll entry or interaction.
+- **Text mask reveals.** Large typography acting as a window to video or animated imagery behind it.
+
+### Layout Upgrades
+- **Broken grid / asymmetry.** Elements that deliberately ignore column structure — overlapping, bleeding off-screen, or offset with calculated randomness.
+- **Whitespace maximization.** Aggressive use of negative space to force focus on a single element.
+- **Parallax card stacks.** Sections that stick and physically stack over each other during scroll.
+- **Split-screen scroll.** Two halves of the screen sliding in opposite directions.
+
+### Motion Upgrades
+- **Smooth scroll with inertia.** Decouple scrolling from browser defaults for a heavier, cinematic feel.
+- **Staggered entry.** Elements cascade in with slight delays, combining Y-axis translation with opacity fade. Never mount everything at once.
+- **Spring physics.** Replace linear easing with spring-based motion for a natural, weighty feel on all interactive elements.
+- **Scroll-driven reveals.** Content entering through expanding masks, wipes, or draw-on SVG paths tied to scroll progress.
+
+### Surface Upgrades
+- **True glassmorphism.** Go beyond `backdrop-filter: blur`. Add a 1px inner border and a subtle inner shadow to simulate edge refraction.
+- **Spotlight borders.** Card borders that illuminate dynamically under the cursor.
+- **Grain and noise overlays.** A fixed, pointer-events-none overlay with subtle noise to break digital flatness.
+- **Colored, tinted shadows.** Shadows that carry the hue of the background rather than using generic black.
+
+## Fix Priority
+
+Apply changes in this order for maximum visual impact with minimum risk:
+
+1. **Font swap** — biggest instant improvement, lowest risk
+2. **Color palette cleanup** — remove clashing or oversaturated colors
+3. **Hover and active states** — makes the interface feel alive
+4. **Layout and spacing** — proper grid, max-width, consistent padding
+5. **Replace generic components** — swap cliche patterns for modern alternatives
+6. **Add loading, empty, and error states** — makes it feel finished
+7. **Polish typography scale and spacing** — the premium final touch
+
+## Rules
+
+- Work with the existing tech stack. Do not migrate frameworks or styling libraries.
+- Do not break existing functionality. Test after every change.
+- Before importing any new library, check the project's dependency file first.
+- If the project uses Tailwind, check the version (v3 vs v4) before modifying config.
+- If the project has no framework, use vanilla CSS.
+- Keep changes reviewable and focused. Small, targeted improvements over big rewrites.

.claude/skills/stitch-design-taste/DESIGN.md

@@ -0,0 +1,121 @@
+# Design System: Taste Standard
+**Skill:** stitch-design-taste
+
+---
+
+## Configuration — Set Your Style
+Adjust these dials before using this design system. They control how creative, dense, and animated the output should be. Pick the level that fits your project.
+
+| Dial | Level | Description |
+|------|-------|-------------|
+| **Creativity** | `8` | `1` = Ultra-minimal, Swiss, silent, monochrome. `5` = Balanced, clean but with personality. `10` = Expressive, editorial, bold typography experiments, inline images in headlines, strong asymmetry. Default: `8` |
+| **Density** | `4` | `1` = Gallery-airy, massive whitespace. `5` = Balanced sections. `10` = Cockpit-dense, data-heavy. Default: `4` |
+| **Variance** | `8` | `1` = Predictable, symmetric grids. `5` = Subtle offsets. `10` = Artsy chaotic, no two sections alike. Default: `8` |
+| **Motion Intent** | `6` | `1` = Static, no animation noted. `5` = Subtle hover/entrance cues. `10` = Cinematic orchestration noted in every component. Default: `6` |
+
+> **How to use:** Change the numbers above to match your project's vibe. At **Creativity 1–3**, the system produces clean, quiet, Notion-like interfaces. At **Creativity 7–10**, expect inline image typography, dramatic scale contrast, and strong editorial layouts. The rest of the rules below adapt to your chosen levels.
+
+---
+
+## 1. Visual Theme & Atmosphere
+A restrained, gallery-airy interface with confident asymmetric layouts and fluid spring-physics motion. The atmosphere is clinical yet warm — like a well-lit architecture studio where every element earns its place through function. Density is balanced (Level 4), variance runs high (Level 8) to prevent symmetrical boredom, and motion is fluid but never theatrical (Level 6). The overall impression: expensive, intentional, alive.
+
+## 2. Color Palette & Roles
+- **Canvas White** (#F9FAFB) — Primary background surface. Warm-neutral, never clinical blue-white
+- **Pure Surface** (#FFFFFF) — Card and container fill. Used with whisper shadow for elevation
+- **Charcoal Ink** (#18181B) — Primary text. Zinc-950 depth — never pure black
+- **Steel Secondary** (#71717A) — Body text, descriptions, metadata. Zinc-500 warmth
+- **Muted Slate** (#94A3B8) — Tertiary text, timestamps, disabled states
+- **Whisper Border** (rgba(226,232,240,0.5)) — Card borders, structural 1px lines. Semi-transparent for depth
+- **Diffused Shadow** (rgba(0,0,0,0.05)) — Card elevation. Wide-spreading, 40px blur, -15px offset. Never harsh
+
+### Accent Selection (Pick ONE per project)
+- **Emerald Signal** (#10B981) — For growth, success, positive data dashboards
+- **Electric Blue** (#3B82F6) — For productivity, SaaS, developer tools
+- **Deep Rose** (#E11D48) — For creative, editorial, fashion-adjacent projects
+- **Amber Warmth** (#F59E0B) — For community, social, warm-toned products
+
+### Banned Colors
+- Purple/Violet neon gradients — the "AI Purple" aesthetic
+- Pure Black (#000000) — always Off-Black or Zinc-950
+- Oversaturated accents above 80% saturation
+- Mixed warm/cool gray systems within one project
+
+## 3. Typography Rules
+- **Display:** `Geist`, `Satoshi`, `Cabinet Grotesk`, or `Outfit` — Track-tight (`-0.025em`), controlled fluid scale, weight-driven hierarchy (700–900). Not screaming. Leading compressed (`1.1`). Alternatives forced — `Inter` is BANNED for premium contexts
+- **Body:** Same family at weight 400 — Relaxed leading (`1.65`), 65ch max-width, Steel Secondary color (#71717A)
+- **Mono:** `Geist Mono` or `JetBrains Mono` — For code blocks, metadata, timestamps. When density exceeds Level 7, all numbers switch to monospace
+- **Scale:** Display at `clamp(2.25rem, 5vw, 3.75rem)`. Body at `1rem/1.125rem`. Mono metadata at `0.8125rem`
+
+### Banned Fonts
+- `Inter` — banned everywhere in premium/creative contexts
+- Generic serif fonts (`Times New Roman`, `Georgia`, `Garamond`, `Palatino`) — BANNED. If serif is needed for editorial/creative, use only distinctive modern serifs like `Fraunces`, `Gambarino`, `Editorial New`, or `Instrument Serif`. Never use default browser serif stacks. Serif is always BANNED in dashboards or software UIs regardless
+
+## 4. Component Stylings
+* **Buttons:** Flat surface, no outer glow. Primary: accent fill with white text. Secondary: ghost/outline. Active state: `-1px translateY` or `scale(0.98)` for tactile push. Hover: subtle background shift, never glow
+* **Cards/Containers:** Generously rounded corners (`2.5rem`). Pure white fill. Whisper border (`1px`, semi-transparent). Diffused shadow (`0 20px 40px -15px rgba(0,0,0,0.05)`). Internal padding `2rem–2.5rem`. Used ONLY when elevation communicates hierarchy — high-density layouts replace cards with `border-top` dividers or negative space
+* **Inputs/Forms:** Label positioned above input. Helper text optional. Error text below in Deep Rose. Focus ring in accent color, `2px` offset. No floating labels. Standard `0.5rem` gap between label-input-error stack
+* **Navigation:** Sleek, sticky. Icons scale on hover (Dock Magnification optional). No hamburger on desktop. Clean horizontal with generous spacing
+* **Loaders:** Skeletal shimmer matching exact layout dimensions and rounded corners. Shifting light reflection across placeholder shapes. Never circular spinners
+* **Empty States:** Composed illustration or icon composition with guidance text. Never just "No data found"
+* **Error States:** Inline, contextual. Red accent underline or border. Clear recovery action
+
+## 5. Hero Section
+The Hero is the first impression — it must be striking, creative, and never generic.
+- **Inline Image Typography:** Embed small, contextual photos or visuals directly between words or letters in the headline. Example: "We build [photo of hands typing] digital [photo of screen] products" — images sit inline at type-height, rounded, acting as visual punctuation between words. This is the signature creative technique
+- **No Overlapping Elements:** Text must never overlap images or other text. Every element has its own clear spatial zone. No z-index stacking of content layers, no absolute-positioned headlines over images. Clean separation always
+- **No Filler Text:** "Scroll to explore", "Swipe down", scroll arrow icons, bouncing chevrons, and any instructional UI chrome are BANNED. The user knows how to scroll. Let the content pull them in naturally
+- **Asymmetric Structure:** Centered Hero layouts are BANNED at this variance level. Use Split Screen (50/50), Left-Aligned text / Right visual, or Asymmetric Whitespace with large empty zones
+- **CTA Restraint:** Maximum one primary CTA button. No secondary "Learn more" links. No redundant micro-copy below the headline
+
+## 6. Layout Principles
+- **Grid-First:** CSS Grid for all structural layouts. Never flexbox percentage math (`calc(33% - 1rem)` is BANNED)
+- **No Overlapping:** Elements must never overlap each other. No absolute-positioned layers stacking content on content. Every element occupies its own grid cell or flow position. Clean, separated spatial zones
+- **Feature Sections:** The "3 equal cards in a row" pattern is BANNED. Use 2-column Zig-Zag, asymmetric Bento grids (2fr 1fr 1fr), or horizontal scroll galleries
+- **Containment:** All content within `max-width: 1400px`, centered. Generous horizontal padding (`1rem` mobile, `2rem` tablet, `4rem` desktop)
+- **Full-Height:** Use `min-height: 100dvh` — never `height: 100vh` (iOS Safari address bar jump)
+- **Bento Architecture:** For feature grids, use Row 1: 3 columns | Row 2: 2 columns (70/30 split). Each tile contains a perpetual micro-animation
+
+## 7. Responsive Rules
+Every screen must work flawlessly across all viewports. **Responsive is not optional — it is a hard requirement. Every single element must be tested at 375px, 768px, and 1440px.**
+- **Mobile-First Collapse (< 768px):** All multi-column layouts collapse to a strict single column. `width: 100%`, `padding: 1rem`, `gap: 1.5rem`. No exceptions
+- **No Horizontal Scroll:** Horizontal overflow on mobile is a critical failure. All elements must fit within viewport width. If any element causes horizontal scroll, the design is broken
+- **Typography Scaling:** Headlines scale down gracefully via `clamp()`. Body text stays `1rem` minimum. Never shrink body below `14px`. Headlines must remain readable on 375px screens
+- **Touch Targets:** All interactive elements minimum `44px` tap target. Generous spacing between clickable items. Buttons must be full-width on mobile
+- **Image Behavior:** Hero and inline images scale proportionally. Inline typography images (photos between words) stack below the headline on mobile instead of inline
+- **Navigation:** Desktop horizontal nav collapses to a clean mobile menu (slide-in or full-screen overlay). No tiny hamburger icons without labels
+- **Cards & Grids:** Bento grids and asymmetric layouts revert to stacked single-column cards with full-width. Maintain internal padding (`1rem`)
+- **Spacing Consistency:** Vertical section gaps reduce proportionally on mobile (`clamp(3rem, 8vw, 6rem)`). Never cramped, never excessively airy
+- **Testing Viewports:** Designs must be verified at: `375px` (iPhone SE), `390px` (iPhone 14), `768px` (iPad), `1024px` (small laptop), `1440px` (desktop)
+
+## 8. Motion & Interaction (Code-Phase Intent)
+> **Note:** Stitch generates static screens — it does not animate. This section documents the **intended motion behavior** so that the coding agent (Antigravity, Cursor, etc.) knows exactly how to implement animations when building the exported design into a live product.
+
+- **Physics Engine:** Spring-based exclusively. `stiffness: 100, damping: 20`. No linear easing anywhere. Premium, weighty feel on all interactive elements
+- **Perpetual Micro-Loops:** Every active dashboard component has an infinite-loop state — Pulse on status dots, Typewriter on search bars, Float on feature icons, Shimmer on loading states
+- **Staggered Orchestration:** Lists and grids mount with cascaded delays (`animation-delay: calc(var(--index) * 100ms)`). Waterfall reveals, never instant mount
+- **Layout Transitions:** Smooth re-ordering via shared element IDs. Items swap positions with physics, simulating real-time intelligence
+- **Hardware Rules:** Animate ONLY `transform` and `opacity`. Never `top`, `left`, `width`, `height`. Grain/noise filters on fixed, pointer-events-none pseudo-elements only
+- **Performance:** CPU-heavy perpetual animations isolated in microscopic leaf components. Never trigger parent re-renders. Target 60fps minimum
+
+## 9. Anti-Patterns (Banned)
+- No emojis — anywhere in UI, code, or alt text
+- No `Inter` font — use `Geist`, `Outfit`, `Cabinet Grotesk`, `Satoshi`
+- No generic serif fonts (`Times New Roman`, `Georgia`, `Garamond`) — if serif is needed, use distinctive modern serifs only (`Fraunces`, `Instrument Serif`)
+- No pure black (`#000000`) — Off-Black or Zinc-950 only
+- No neon outer glows or default box-shadow glows
+- No oversaturated accent colors above 80%
+- No excessive gradient text on large headers
+- No custom mouse cursors
+- No overlapping elements — text never overlaps images or other content. Clean spatial separation always
+- No 3-column equal card layouts for features
+- No centered Hero sections (at this variance level)
+- No filler UI text: "Scroll to explore", "Swipe down", "Discover more below", scroll arrows, bouncing chevrons — all BANNED
+- No generic names: "John Doe", "Sarah Chan", "Acme", "Nexus", "SmartFlow"
+- No fake round numbers: `99.99%`, `50%`, `1234567` — use organic data: `47.2%`, `+1 (312) 847-1928`
+- No AI copywriting clichés: "Elevate", "Seamless", "Unleash", "Next-Gen", "Revolutionize"
+- No broken Unsplash links — use `picsum.photos/seed/{id}/800/600` or SVG UI Avatars
+- No generic `shadcn/ui` defaults — customize radii, colors, shadows to match this system
+- No `z-index` spam — use only for Navbar, Modal, Overlay layer contexts
+- No `h-screen` — always `min-h-[100dvh]`
+- No circular loading spinners — skeletal shimmer only

.claude/skills/stitch-design-taste/SKILL.md

@@ -0,0 +1,184 @@
+---
+name: stitch-design-taste
+description: Semantic Design System Skill for Google Stitch. Generates agent-friendly DESIGN.md files that enforce premium, anti-generic UI standards — strict typography, calibrated color, asymmetric layouts, perpetual micro-motion, and hardware-accelerated performance.
+---
+
+# Stitch Design Taste — Semantic Design System Skill
+
+## Overview
+This skill generates `DESIGN.md` files optimized for Google Stitch screen generation. It translates the battle-tested anti-slop frontend engineering directives into Stitch's native semantic design language — descriptive, natural-language rules paired with precise values that Stitch's AI agent can interpret to produce premium, non-generic interfaces.
+
+The generated `DESIGN.md` serves as the **single source of truth** for prompting Stitch to generate new screens that align with a curated, high-agency design language. Stitch interprets design through **"Visual Descriptions"** supported by specific color values, typography specs, and component behaviors.
+
+## Prerequisites
+- Access to Google Stitch via [labs.google/stitch](https://labs.google/stitch)
+- Optionally: Stitch MCP Server for programmatic integration with Cursor, Antigravity, or Gemini CLI
+
+## The Goal
+Generate a `DESIGN.md` file that encodes:
+1. **Visual atmosphere** — the mood, density, and design philosophy
+2. **Color calibration** — neutrals, accents, and banned patterns with hex codes
+3. **Typographic architecture** — font stacks, scale hierarchy, and anti-patterns
+4. **Component behaviors** — buttons, cards, inputs with interaction states
+5. **Layout principles** — grid systems, spacing philosophy, responsive strategy
+6. **Motion philosophy** — animation engine specs, spring physics, perpetual micro-interactions
+7. **Anti-patterns** — explicit list of banned AI design clichés
+
+## Analysis & Synthesis Instructions
+
+### 1. Define the Atmosphere
+Evaluate the target project's intent. Use evocative adjectives from the taste spectrum:
+- **Density:** "Art Gallery Airy" (1–3) → "Daily App Balanced" (4–7) → "Cockpit Dense" (8–10)
+- **Variance:** "Predictable Symmetric" (1–3) → "Offset Asymmetric" (4–7) → "Artsy Chaotic" (8–10)
+- **Motion:** "Static Restrained" (1–3) → "Fluid CSS" (4–7) → "Cinematic Choreography" (8–10)
+
+Default baseline: Variance 8, Motion 6, Density 4. Adapt dynamically based on user's vibe description.
+
+### 2. Map the Color Palette
+For each color provide: **Descriptive Name** + **Hex Code** + **Functional Role**.
+
+**Mandatory constraints:**
+- Maximum 1 accent color. Saturation below 80%
+- The "AI Purple/Blue Neon" aesthetic is strictly BANNED — no purple button glows, no neon gradients
+- Use absolute neutral bases (Zinc/Slate) with high-contrast singular accents
+- Stick to one palette for the entire output — no warm/cool gray fluctuation
+- Never use pure black (`#000000`) — use Off-Black, Zinc-950, or Charcoal
+
+### 3. Establish Typography Rules
+- **Display/Headlines:** Track-tight, controlled scale. Not screaming. Hierarchy through weight and color, not just massive size
+- **Body:** Relaxed leading, max 65 characters per line
+- **Font Selection:** `Inter` is BANNED for premium/creative contexts. Force unique character: `Geist`, `Outfit`, `Cabinet Grotesk`, or `Satoshi`
+- **Serif Ban:** Generic serif fonts (`Times New Roman`, `Georgia`, `Garamond`, `Palatino`) are BANNED. If serif is needed for editorial/creative contexts, use only distinctive modern serifs: `Fraunces`, `Gambarino`, `Editorial New`, or `Instrument Serif`. Serif is always BANNED in dashboards or software UIs
+- **Dashboard Constraint:** Use Sans-Serif pairings exclusively (`Geist` + `Geist Mono` or `Satoshi` + `JetBrains Mono`)
+- **High-Density Override:** When density exceeds 7, all numbers must use Monospace
+
+### 4. Define the Hero Section
+The Hero is the first impression and must be creative, striking, and never generic:
+- **Inline Image Typography:** Embed small, contextual photos or visuals directly between words or letters in the headline. Images sit inline at type-height, rounded, acting as visual punctuation. This is the signature creative technique
+- **No Overlapping:** Text must never overlap images or other text. Every element occupies its own clean spatial zone
+- **No Filler Text:** "Scroll to explore", "Swipe down", scroll arrow icons, bouncing chevrons are BANNED. The content should pull users in naturally
+- **Asymmetric Structure:** Centered Hero layouts BANNED when variance exceeds 4
+- **CTA Restraint:** Maximum one primary CTA. No secondary "Learn more" links
+
+### 5. Describe Component Stylings
+For each component type, describe shape, color, shadow depth, and interaction behavior:
+- **Buttons:** Tactile push feedback on active state. No neon outer glows. No custom mouse cursors
+- **Cards:** Use ONLY when elevation communicates hierarchy. Tint shadows to background hue. For high-density layouts, replace cards with border-top dividers or negative space
+- **Inputs/Forms:** Label above input, helper text optional, error text below. Standard gap spacing
+- **Loading States:** Skeletal loaders matching layout dimensions — no generic circular spinners
+- **Empty States:** Composed compositions indicating how to populate data
+- **Error States:** Clear, inline error reporting
+
+### 6. Define Layout Principles
+- No overlapping elements — every element occupies its own clear spatial zone. No absolute-positioned content stacking
+- Centered Hero sections are BANNED when variance exceeds 4 — force Split Screen, Left-Aligned, or Asymmetric Whitespace
+- The generic "3 equal cards horizontally" feature row is BANNED — use 2-column Zig-Zag, asymmetric grid, or horizontal scroll
+- CSS Grid over Flexbox math — never use `calc()` percentage hacks
+- Contain layouts using max-width constraints (e.g., 1400px centered)
+- Full-height sections must use `min-h-[100dvh]` — never `h-screen` (iOS Safari catastrophic jump)
+
+### 7. Define Responsive Rules
+Every design must work across all viewports:
+- **Mobile-First Collapse (< 768px):** All multi-column layouts collapse to single column. No exceptions
+- **No Horizontal Scroll:** Horizontal overflow on mobile is a critical failure
+- **Typography Scaling:** Headlines scale via `clamp()`. Body text minimum `1rem`/`14px`
+- **Touch Targets:** All interactive elements minimum `44px` tap target
+- **Image Behavior:** Inline typography images (photos between words) stack below headline on mobile
+- **Navigation:** Desktop horizontal nav collapses to clean mobile menu
+- **Spacing:** Vertical section gaps reduce proportionally (`clamp(3rem, 8vw, 6rem)`)
+
+### 8. Encode Motion Philosophy
+- **Spring Physics default:** `stiffness: 100, damping: 20` — premium, weighty feel. No linear easing
+- **Perpetual Micro-Interactions:** Every active component should have an infinite loop state (Pulse, Typewriter, Float, Shimmer)
+- **Staggered Orchestration:** Never mount lists instantly — use cascade delays for waterfall reveals
+- **Performance:** Animate exclusively via `transform` and `opacity`. Never animate `top`, `left`, `width`, `height`. Grain/noise filters on fixed pseudo-elements only
+
+### 9. List Anti-Patterns (AI Tells)
+Encode these as explicit "NEVER DO" rules in the DESIGN.md:
+- No emojis anywhere
+- No `Inter` font
+- No generic serif fonts (`Times New Roman`, `Georgia`, `Garamond`) — distinctive modern serifs only if needed
+- No pure black (`#000000`)
+- No neon/outer glow shadows
+- No oversaturated accents
+- No excessive gradient text on large headers
+- No custom mouse cursors
+- No overlapping elements — clean spatial separation always
+- No 3-column equal card layouts
+- No generic names ("John Doe", "Acme", "Nexus")
+- No fake round numbers (`99.99%`, `50%`)
+- No AI copywriting clichés ("Elevate", "Seamless", "Unleash", "Next-Gen")
+- No filler UI text: "Scroll to explore", "Swipe down", scroll arrows, bouncing chevrons
+- No broken Unsplash links — use `picsum.photos` or SVG avatars
+- No centered Hero sections (for high-variance projects)
+
+## Output Format (DESIGN.md Structure)
+
+```markdown
+# Design System: [Project Title]
+
+## 1. Visual Theme & Atmosphere
+(Evocative description of the mood, density, variance, and motion intensity.
+Example: "A restrained, gallery-airy interface with confident asymmetric layouts
+and fluid spring-physics motion. The atmosphere is clinical yet warm — like a
+well-lit architecture studio.")
+
+## 2. Color Palette & Roles
+- **Canvas White** (#F9FAFB) — Primary background surface
+- **Pure Surface** (#FFFFFF) — Card and container fill
+- **Charcoal Ink** (#18181B) — Primary text, Zinc-950 depth
+- **Muted Steel** (#71717A) — Secondary text, descriptions, metadata
+- **Whisper Border** (rgba(226,232,240,0.5)) — Card borders, 1px structural lines
+- **[Accent Name]** (#XXXXXX) — Single accent for CTAs, active states, focus rings
+(Max 1 accent. Saturation < 80%. No purple/neon.)
+
+## 3. Typography Rules
+- **Display:** [Font Name] — Track-tight, controlled scale, weight-driven hierarchy
+- **Body:** [Font Name] — Relaxed leading, 65ch max-width, neutral secondary color
+- **Mono:** [Font Name] — For code, metadata, timestamps, high-density numbers
+- **Banned:** Inter, generic system fonts for premium contexts. Serif fonts banned in dashboards.
+
+## 4. Component Stylings
+* **Buttons:** Flat, no outer glow. Tactile -1px translate on active. Accent fill for primary, ghost/outline for secondary.
+* **Cards:** Generously rounded corners (2.5rem). Diffused whisper shadow. Used only when elevation serves hierarchy. High-density: replace with border-top dividers.
+* **Inputs:** Label above, error below. Focus ring in accent color. No floating labels.
+* **Loaders:** Skeletal shimmer matching exact layout dimensions. No circular spinners.
+* **Empty States:** Composed, illustrated compositions — not just "No data" text.
+
+## 5. Layout Principles
+(Grid-first responsive architecture. Asymmetric splits for Hero sections.
+Strict single-column collapse below 768px. Max-width containment.
+No flexbox percentage math. Generous internal padding.)
+
+## 6. Motion & Interaction
+(Spring physics for all interactive elements. Staggered cascade reveals.
+Perpetual micro-loops on active dashboard components. Hardware-accelerated
+transforms only. Isolated Client Components for CPU-heavy animations.)
+
+## 7. Anti-Patterns (Banned)
+(Explicit list of forbidden patterns: no emojis, no Inter, no pure black,
+no neon glows, no 3-column equal grids, no AI copywriting clichés,
+no generic placeholder names, no broken image links.)
+```
+
+## Best Practices
+- **Be Descriptive:** "Deep Charcoal Ink (#18181B)" — not just "dark text"
+- **Be Functional:** Explain what each element is used for
+- **Be Consistent:** Same terminology throughout the document
+- **Be Precise:** Include exact hex codes, rem values, pixel values in parentheses
+- **Be Opinionated:** This is not a neutral template — it enforces a specific, premium aesthetic
+
+## Tips for Success
+1. Start with the atmosphere — understand the vibe before detailing tokens
+2. Look for patterns — identify consistent spacing, sizing, and styling
+3. Think semantically — name colors by purpose, not just appearance
+4. Consider hierarchy — document how visual weight communicates importance
+5. Encode the bans — anti-patterns are as important as the rules themselves
+
+## Common Pitfalls to Avoid
+- Using technical jargon without translation ("rounded-xl" instead of "generously rounded corners")
+- Omitting hex codes or using only descriptive names
+- Forgetting functional roles of design elements
+- Being too vague in atmosphere descriptions
+- Ignoring the anti-pattern list — these are what make the output premium
+- Defaulting to generic "safe" designs instead of enforcing the curated aesthetic

.dockerignore

@@ -30,6 +30,8 @@ public/build
 public/storage
 public/hot
 
+_ARCHIVE
+
 db_data
 redis_data
 
@@ -44,3 +46,4 @@ docker-compose.override.yml
 .idea
 .vscode
 .phpunit.result.cache
+.phpunit.cache

.env.example

@@ -34,6 +34,10 @@ APP_URL=http://192.0.2.10:8080
 # I dati personali dei proclamatori sono cifrati con questa chiave: se la
 # perdi non sono piu' leggibili nemmeno avendo il backup del database.
 # Conservala in un password manager.
+# Una copia sta nel volume dello storage: se questo valore cambia e non
+# coincide con la copia, il container si rifiuta di partire invece di rendere
+# illeggibili i dati. Per un cambio voluto aggiungi APP_KEY_ROTATE=1 (la
+# chiave vecchia viene conservata accanto alla copia), poi toglila.
 APP_KEY=
 
 LOG_CHANNEL=stderr
@@ -81,6 +85,31 @@ CACHE_STORE=redis
 SESSION_DRIVER=redis
 QUEUE_CONNECTION=redis
 
+# -----------------------------------------------------------------------------
+# Dimensione massima dei file caricati (MB)
+# -----------------------------------------------------------------------------
+# Governa insieme nginx (client_max_body_size), PHP (upload_max_filesize e
+# post_max_size) e la validazione dell'applicazione: li genera l'entrypoint da
+# questo unico valore, cosi' non possono andare fuori sincrono.
+#
+# Il file piu' grande che passa di qui e' il pacchetto di ripristino, che
+# contiene tutti i PDF dei territori: con qualche centinaio di mappe si arriva
+# facilmente a oltre un giga. Se un caricamento muore senza spiegazioni e la
+# barra si pianta, e' quasi sempre questo il limite che si e' incontrato.
+#
+# Alzarlo non costa memoria: nginx accumula il corpo su disco e PHP lavora su un
+# file temporaneo. Serve pero' spazio libero nel volume.
+MAX_UPLOAD_MB=2048
+
+# Renderer delle piantine (pagina "Piantine", solo amministratore).
+#
+# E' il container `map-renderer` del compose: il default punta gia' li' e non
+# serve impostare niente. Le variabili esistono per chi volesse spostare il
+# renderer altrove o allungare il tempo concesso a un singolo rendering
+# (comprende il download delle tessere OSM non ancora in cache).
+# MAP_RENDERER_URL=http://map-renderer:3000
+# MAP_RENDERER_TIMEOUT=180
+
 # DEVE essere false se accedi in HTTP (tipicamente per IP:porta).
 #
 # Con true, il cookie di sessione viene marcato "secure" e il browser non lo
@@ -97,15 +126,24 @@ SESSION_SECURE_COOKIE=false
 # -----------------------------------------------------------------------------
 # Posta
 # -----------------------------------------------------------------------------
+# Il server di posta si configura di solito dall'applicazione (Impostazioni →
+# Server di posta): se lì è compilato, questi valori vengono ignorati.
+# Servono le email di conferma: senza posta gli utenti non possono confermare
+# il loro indirizzo e il loro account non funziona.
+#
 # In produzione: SMTP esterno.
 # In locale con --profile dev: MAIL_HOST=mailpit, MAIL_PORT=1025
 # Per disattivare del tutto l'invio: MAIL_MAILER=log
+#
+# MAIL_SCHEME: vuoto (sceglie da solo: STARTTLS sulla 587, SSL sulla 465),
+# oppure smtp / smtps. "tls" non è un valore valido con Laravel 11 e fa
+# fallire ogni invio.
 MAIL_MAILER=smtp
 MAIL_HOST=
 MAIL_PORT=587
 MAIL_USERNAME=
 MAIL_PASSWORD=
-MAIL_SCHEME=tls
+MAIL_SCHEME=
 MAIL_FROM_ADDRESS=noreply@example.org
 MAIL_FROM_NAME="${APP_NAME}"
 

.gitattributes

@@ -0,0 +1,3 @@
+# Gli script finiscono in container Linux: con CRLF (core.autocrlf su
+# Windows) il kernel non trova l'interprete e il container non parte.
+*.sh text eol=lf

.gitignore

@@ -9,16 +9,24 @@
 /storage/app/livewire-tmp/*.*
 /storage/logs/
 /storage/framework/
+/storage/app/public/territori-thumbnails/*.png
 /bootstrap/cache/
 /public/hot
 /public/storage
 /public/build/
 /.phpunit.result.cache
+/.phpunit.cache/
 /.idea/
 /.vscode/
 *.swp
 *.swo
 *.sql
+*.pdf
+# Eccezione: i moduli ufficiali usati come matrice per i template di stampa
+# (resources/views/pdf/*) vanno versionati, altrimenti il template perde il
+# riferimento da cui è stato ricostruito.
+!resources/pdf/*.pdf
 docker-compose.override.yml
 db_data/
 redis_data/
+.claude

README.md

@@ -1,8 +1,11 @@
 # TerManager2
 
 Applicazione web per la gestione dell'assegnazione e del rientro dei territori
-(cartoline) di congregazione, con statistiche di percorrenza, campagne speciali
-e registro storico completo.
+(cartoline) di congregazione, con statistiche di percorrenza, campagne speciali,
+gruppi di servizio (un sorvegliante distribuisce ai membri un pacchetto di
+territori), un modulo pubblico con cui i proclamatori chiedono un territorio o
+ne annunciano la riconsegna, l'elenco delle cartoline cartacee fuori, il
+modulo S-13 per email ogni mese e registro storico completo.
 
 I dati personali dei proclamatori sono **cifrati nel database**, e ogni
 operazione è tracciata in un **audit log** consultabile.
@@ -14,7 +17,7 @@ operazione è tracciata in un **audit log** consultabile.
 **Per iniziare**
 - [Deploy su Dokploy](#deploy-su-dokploy) — la via consigliata per la produzione
 - [Deploy su altri sistemi](#deploy-su-altri-sistemi) — Coolify, Portainer, server con Docker
-- [Sviluppo locale](#sviluppo-locale)
+- [Sviluppo locale](#sviluppo-locale) — compreso come lanciare i [test automatici](#test-automatici)
 
 **Gestione quotidiana**
 - [Variabili d'ambiente](#variabili-dambiente)
@@ -49,7 +52,7 @@ eseguito né `composer install` né `npm build` all'avvio.
 |----------------|------------------------------------------------|---------|
 | `app`          | nginx + php-fpm — l'applicazione               | via Traefik |
 | `queue-worker` | Job in coda (import PDF massivi)               | no |
-| `scheduler`    | Task pianificati (pulizia audit log)           | no |
+| `scheduler`    | Task pianificati (pulizie, S-13 mensile)       | no |
 | `mariadb`      | Database                                        | no |
 | `redis`        | Cache, sessioni, code                           | no |
 
@@ -302,6 +305,52 @@ npm install
 npm run dev
 ```
 
+### Test automatici
+
+La suite gira in un container dedicato: l'immagine di produzione installa le
+dipendenze senza quelle di sviluppo, quindi PHPUnit lì dentro non c'è.
+
+```bash
+docker compose --profile test run --build --rm test
+
+# una sola classe
+docker compose --profile test run --build --rm test --filter BackupArchiveTest
+
+# un solo gruppo
+docker compose --profile test run --build --rm test --testsuite Unit
+```
+
+Il container esce col codice di PHPUnit, quindi la riga di comando si incatena
+come qualsiasi altro comando.
+
+**`--build` non è facoltativo.** Il sorgente non è montato: senza ricostruire,
+si eseguono i test dell'ultima immagine costruita, che possono essere di due
+modifiche fa. Ometterlo ha senso solo per rilanciare la stessa suite subito
+dopo, quando si sa che nulla è cambiato.
+
+Cosa serve sapere:
+
+- **Non serve nient'altro acceso.** `phpunit.xml` impone SQLite in memoria,
+  cache `array` e code `sync`: la suite passa a stack spento e non tocca né il
+  database di sviluppo né il volume `storage_data`.
+- **`APP_KEY` di test è fissa e scritta in `phpunit.xml`.** Serve perché nome e
+  cognome dei proclamatori sono cifrati: senza chiave nemmeno un test che non
+  parla di cifratura riuscirebbe a scrivere una riga. Non ha alcun rapporto con
+  la chiave di produzione.
+- **SQLite non è MariaDB.** Resta un punto che usa SQL specifico di MySQL —
+  `CAST(... AS UNSIGNED)` nell'ordinamento del Registro — e che quindi va
+  provato sullo stack vero, non qui.
+
+La logica JavaScript senza DOM (la ricerca nei campi di scelta,
+`resources/js/scelta.js`) ha i suoi test in `tests/js/`, con il test runner di
+Node:
+
+```bash
+npm run test:js
+# oppure, senza Node installato:
+docker run --rm -v "$PWD":/app -w /app node:20-alpine node --test tests/js/
+```
+
 ---
 
 ## Variabili d'ambiente
@@ -330,6 +379,7 @@ ridichiara le variabili applicative: le prende dal `.env` così com'è.
 | `APP_TIMEZONE`               | `Europe/Rome`  | Fuso orario                           |
 | `LOG_LEVEL`                  | `warning`      | `debug` per diagnosticare             |
 | `SESSION_SECURE_COOKIE`      | `false`        | `true` solo servendo in HTTPS         |
+| `MAX_UPLOAD_MB`              | `2048`         | Tetto dei file caricati: governa insieme nginx, PHP e la validazione |
 | `APP_BIND`                   | `0.0.0.0`      | `127.0.0.1` dietro un reverse proxy   |
 | `APP_PORT`                   | `8080`         | Porta dell'applicazione sull'host     |
 | `DB_BIND`                    | `127.0.0.1`    | Interfaccia della porta MariaDB       |
@@ -363,24 +413,27 @@ Redis, quindi puntarli su un driver diverso interrompe l'elaborazione dei job.
 Configurabili dall'interfaccia (**Impostazioni**, permesso `settings.manage`),
 non da variabili d'ambiente:
 
-| Impostazione                   | Descrizione                                          |
-|--------------------------------|------------------------------------------------------|
-| Nome congregazione             | Mostrato nell'intestazione e nei PDF                 |
-| Logo                           | Immagine nell'intestazione                           |
-| URL pubblico base              | Base dei link PDF condivisibili                      |
-| Giorni giacenza "da assegnare" | Soglia oltre cui un territorio è da assegnare        |
-| Mesi giacenza "prioritari"     | Soglia oltre cui un territorio diventa prioritario   |
-| Giorni per "smarrito"          | Soglia oltre cui un'assegnazione è da rientrare      |
-| Elementi nelle liste della home| Quanti record mostrare nelle tre liste rapide        |
-| Validità link PDF (mesi)       | Scadenza dei link pubblici alle cartoline            |
-| Download PDF visibile          | Mostra o nasconde il pulsante di download            |
-| Retention audit log (giorni)   | Dopo quanti giorni i log vengono cancellati          |
+| Impostazione                       | Descrizione                                          |
+|------------------------------------|------------------------------------------------------|
+| Nome congregazione                 | Mostrato nell'intestazione, nei PDF e nell'informativa |
+| Soglia da assegnare (giorni)       | Dopo quanti giorni dal rientro un territorio è "da assegnare" |
+| Soglia priorità (giorni)           | Dopo quanti giorni dal rientro un territorio diventa prioritario |
+| Soglia rientro (giorni)            | Oltre questa un'assegnazione è "da rientrare"; è anche la durata del link alla piantina |
+| Limite liste Home                  | Quanti territori mostrare nelle due liste della Home |
+| "Scarica PDF" nel viewer           | Mostra o nasconde il pulsante di download a chi apre il link |
+| Conservazione audit (giorni)       | Dopo quanti giorni le voci del registro delle attività si cancellano |
+
+Il server di posta ha una pagina sua (*Impostazioni → Server di posta*). Il
+logo nell'intestazione, se c'è, arriva da un backup: la pagina non lo carica.
 
 ---
 
 ## Aggiornamenti
 
-Push su `main` → **Deploy** su Dokploy. Ad ogni avvio il container:
+Push su `main` → **Deploy** su Dokploy. Se l'autodeploy non parte entro un
+paio di minuti (succede: vedi HANDOFF, *Dove gira davvero*), il deploy si
+avvia a mano dall'interfaccia o con `compose.deploy`. Ad ogni avvio il
+container:
 
 1. ricrea le directory di storage e risolve `APP_KEY`
 2. attende il database
@@ -397,7 +450,114 @@ Un aggiornamento ordinario non richiede alcun intervento manuale.
 
 ## Backup e ripristino
 
-### Cosa salvare
+### Com'è fatta la pagina *Backup e import*
+
+Cinque zone numerate, in ordine di quanto sono definitive. L'indice in cima
+salta su ciascuna evidenziandola:
+
+| # | Zona | A cosa serve |
+|---|------|--------------|
+| 1 | Backup completo | Crea e scarica il pacchetto `.zip` |
+| 2 | Ripristina da backup | Ricarica un pacchetto: **sostituisce** dati e file |
+| 3 | Import PDF territori | Associa i PDF ai territori (da archivio ZIP o da cartella) |
+| 4 | Dati in formato XML | Esporta/importa i soli dati, converte i dump della vecchia app |
+| 5 | Zona pericolosa | Azzera l'installazione |
+
+In fondo alla finestra c'è **una sola console**, comune a tutte le operazioni:
+si apre da sé quando qualcosa parte, scorre da sola man mano che arrivano le
+righe e riporta sia quello che succede nel browser (file scelto, avanzamento del
+caricamento, codici HTTP, timeout) sia quello che succede sul server, in ordine
+di tempo e con la sorgente accanto a ogni riga. Il pulsante **Copia** serve
+proprio a questo: il primo passo di ogni diagnosi è farsi mandare quel testo.
+
+Se torni indietro a leggere, lo scorrimento automatico si sospende e compare
+*Torna in fondo*.
+
+### Dall'applicazione: pacchetto `.zip` (consigliato)
+
+*Backup e import* → **Crea e scarica backup**. Produce un unico `.zip` con
+tutti i dati gestionali, gli utenti e tutti i file caricati (PDF dei territori,
+miniature, logo). È la via da usare per spostare o rimettere in piedi
+un'installazione senza toccare i container.
+
+L'archivio si prepara in background e la console mostra l'avanzamento reale
+(file compressi / file totali); il download parte da solo appena è pronto.
+Stessa cosa per il ripristino: prima la barra di caricamento del pacchetto,
+accanto al pulsante, poi le fasi di lavoro nella console (estrazione, database,
+file).
+
+Sulla stessa pagina, **Ripristina backup** ricarica il pacchetto: sostituisce i
+dati gestionali correnti *e* i file caricati.
+
+> **Dopo un ripristino tutti gli utenti — amministratore compreso — devono
+> impostare una nuova password.** Il pacchetto contiene gli hash delle password
+> di ogni account: chi lo ha avuto in mano ha potuto tentarne il crack offline,
+> quindi le vecchie credenziali non sono più considerate sicure. Al primo
+> accesso l'applicazione resta bloccata sulla schermata di cambio password.
+
+Il pacchetto **non** contiene `APP_KEY`: i nomi dei proclamatori sono cifrati
+con quella chiave, quindi il ripristino va fatto su un'installazione che ha la
+**stessa** `APP_KEY` di quando il backup è stato creato.
+
+Il tetto per l'upload lo decide **`MAX_UPLOAD_MB`** nel `.env` (default: 2048,
+cioè 2 GB). Da quel valore l'entrypoint genera `client_max_body_size` per nginx
+e `upload_max_filesize`/`post_max_size` per PHP, e la validazione lo rilegge:
+un solo numero per tutta la catena.
+
+> Se un caricamento si pianta a una percentuale bassa **senza messaggi**, è
+> quasi sempre questo il limite. Superato il tetto nginx risponde `413` dopo
+> aver accettato zero byte: il browser si vede chiudere la connessione a metà
+> invio e la barra resta ferma. Dalla versione attuale la pagina controlla la
+> dimensione *prima* di iniziare e lo dice subito, ma se aggiorni un'installazione
+> vecchia il sintomo è quello.
+
+Per alzarlo servono un `MAX_UPLOAD_MB` più grande **e** un redeploy (i limiti si
+scrivono all'avvio del container). Alzarlo non costa memoria — nginx accumula il
+corpo su disco e PHP lavora su un file temporaneo — ma serve spazio libero nel
+volume. Oltre qualche giga conviene comunque il backup dei volumi qui sotto: un
+upload lunghissimo da browser è fragile.
+
+> **Se il dominio passa da Cloudflare, comanda Cloudflare.** Sul piano free
+> rifiuta i corpi di richiesta oltre **100 MB**, e lo fa in base al
+> `Content-Length`: il `413` arriva dopo appena un megabyte spedito, quindi il
+> pacchetto **non raggiunge mai nginx** e `MAX_UPLOAD_MB` non sposta nulla.
+> C'è anche un tetto di 100 secondi: un caricamento lento può fallire con `524`
+> pur restando sotto il limite di dimensione.
+>
+> Per superarlo: togliere il dominio da Cloudflare (DNS-only), anche solo su un
+> sottodominio d'amministrazione; oppure caricare puntando direttamente all'IP
+> dell'origine; oppure usare il ripristino dai volumi qui sotto. Il piano
+> Business arriva a 200 MB, spesso ancora insufficienti.
+>
+> La **console** in fondo alla finestra mostra il codice HTTP ricevuto: se
+> leggi `413` con un pacchetto sotto `MAX_UPLOAD_MB`, il tetto è a monte.
+
+### Zona pericolosa: azzera tutto
+
+Zona 5, in fondo alla stessa pagina: **Scarica backup e azzera tutto** riporta
+l'applicazione allo stato di installazione appena eseguita. Va scritto
+`AZZERA TUTTO` per sbloccare il pulsante, e l'operazione procede in due tempi:
+
+1. Viene creato e scaricato un backup completo di tutto ciò che c'è.
+2. L'operazione **si ferma e aspetta**, e la richiesta di conferma compare lì
+   nella zona 5, sotto il pulsante che l'ha avviata: controlli il file
+   scaricato, digiti la **tua password** e confermi con un secondo clic. Fino a
+   lì non viene toccato nulla, e puoi annullare. Dopo cinque password sbagliate
+   l'azzeramento resta bloccato per 5 minuti (l'accesso all'applicazione no).
+3. Solo dopo la conferma vengono eliminati territori, proclamatori,
+   assegnazioni, campagne, zone, tipologie, anni di servizio, il registro
+   attività e tutti i file caricati; le impostazioni tornano ai default e i
+   ruoli vengono riseminati.
+
+> **Tutti gli altri utenti vengono eliminati.** Resta solo l'account
+> dell'amministratore che ha eseguito l'operazione, con la sua password
+> attuale — come un'installazione nuova, che ha un amministratore solo.
+> Cancellarli tutti lascerebbe l'applicazione senza nessuno che possa
+> accedere fino al riavvio del container.
+
+Il backup scaricato al punto 1 è l'unico modo per tornare indietro.
+
+### Dai volumi: cosa salvare
 
 | Volume         | Contenuto                                            | Nel backup |
 |----------------|------------------------------------------------------|:----------:|
@@ -468,10 +628,26 @@ docker exec -it <app> php artisan app:create-initial-admin \
 # Pulizia manuale dell'audit log
 docker exec -it <app> php artisan audit:cleanup
 
+# Pulizia manuale degli archivi di backup residui (default: più vecchi di 24h)
+docker exec -it <app> php artisan backup:cleanup
+docker exec -it <app> php artisan backup:cleanup --ore=0   # tutti
+
+# Pulizia manuale delle richieste dal modulo pubblico gestite da più di 90 giorni
+docker exec -it <app> php artisan richieste:pulizia
+
+# Mandare subito il modulo S-13 agli amministratori (anno in corso, o un altro)
+docker exec -it <app> php artisan registro:invia-s13
+docker exec -it <app> php artisan registro:invia-s13 --anno=2025-2026
+
 # Svuotare le cache
 docker exec -it <app> php artisan optimize:clear
 ```
 
+Le pulizie girano già da sole ogni notte e il modulo S-13 parte da solo
+l'ultima domenica del mese alle 8 (container `scheduler`); i comandi qui sopra
+servono solo per anticiparli. Senza un server di posta funzionante il modulo
+S-13 non parte (il comando lo dice).
+
 ---
 
 ## Troubleshooting
@@ -526,14 +702,24 @@ docker compose --profile dev up -d --build
 - Anno teocratico corrente (creato automaticamente, settembre → agosto)
 - Media mensile di percorrenza e durata media delle assegnazioni
 - Campagna attiva con barra di progresso
-- Tre liste rapide con azione diretta: **da assegnare**, **prioritari**,
-  **da rientrare**
+- Due liste rapide con azione diretta: **da assegnare** (prima i prioritari,
+  con il badge ★, poi quelli fermi da più tempo) e **da rientrare**; quando
+  l'elenco è troncato, **"Vedi tutti"** è un pulsante in testata che apre
+  l'elenco territori già filtrato. "Assegna →" apre la pagina *Assegna* con
+  il territorio scelto e senza l'elenco dei territori assegnati
+- **Richieste** dal modulo pubblico (amministratore e assistenti): vedi
+  [Richieste dal modulo pubblico](#richieste-dal-modulo-pubblico)
 
 ### Territori
 - CRUD completo con upload PDF e miniatura generata automaticamente
-- Filtri per zona, tipologia e stato
+- **"Nuovo territorio"** apre il designer delle piantine già in disegno: il
+  territorio si crea dal confine disegnato (per chi non è amministratore resta
+  il form)
+- Filtri per zona, tipologia e stato, conservati nell'indirizzo della pagina
 - Badge di stato colorati e indicatore di priorità (manuale o automatica)
-- Dettaglio con visualizzatore PDF e storico assegnazioni per anno teocratico
+- Dettaglio con visualizzatore PDF e storico assegnazioni per anno teocratico:
+  una tabella sola con le colonne in linea, l'anno come riga di separazione,
+  dal più recente (lo stesso nella scheda del proclamatore)
 - Link PDF pubblico condivisibile, a scadenza configurabile
 - Soft delete con cestino (ripristino o eliminazione definitiva)
 - Import massivo di PDF da cartella o archivio ZIP, elaborato in background
@@ -545,12 +731,124 @@ docker compose --profile dev up -d --build
 - Soft delete con cestino
 
 ### Assegnazione e rientro
-- Selezione territorio disponibile e proclamatore attivo
+- **Scelta con ricerca** di territorio e proclamatore (anche nel Registro e nel
+  designer delle piantine): si scrive e compaiono le proposte più vicine —
+  uguale, inizia con, contiene, errore di battitura ("forse cercavi") — con
+  le parole in qualsiasi ordine, senza badare a maiuscole e accenti. Campo
+  vuoto: l'elenco completo. Pensata anche per il telefono
+- I territori già assegnati si trovano cercando ("già assegnato a …") ma non
+  si possono scegliere; l'anteprima della miniatura segue la scelta
 - Anno teocratico rilevato automaticamente dalla data
 - Validazione: territorio non già assegnato, entrambi attivi
+- **Invio del link dopo l'assegnazione**: una finestra chiede il canale —
+  *Copia link*, oppure *Condividi…* (il menu di condivisione del telefono:
+  WhatsApp, Telegram, SMS…, dove il browser lo offre) — e se il link è stato
+  inviato. Il destinatario lo sceglie chi usa l'app dai propri contatti: i
+  proclamatori non hanno numero né email. Solo dopo la risposta si va avanti;
+  altrimenti l'assegnazione resta segnalata **"Link ancora da inviare"**, con
+  "Invia link" per riprendere. Anche dall'elenco dei territori assegnati si
+  può copiare o condividere il link
+- L'elenco dei territori assegnati si carica subito dopo la pagina e si filtra
+  nel browser, senza attese; ogni territorio ha il pulsante **Rientro**, che
+  porta alla registrazione del rientro e poi torna all'elenco. Aperta da
+  "Assegna →" della Home, la pagina mostra solo il modulo, senza l'elenco
 - Rientro con calcolo automatico dei giorni
-- **Prompt campagna**: se il rientro ricade nel periodo di una campagna, viene
-  chiesto se conteggiarlo
+- **Prompt campagna**: se il territorio era fuori durante una campagna viene
+  chiesto se è stato percorso per la campagna; oltre la soglia "da rientrare"
+  compare un avviso di tempo di percorrenza molto alto
+- **Dopo una conferma o un annulla si torna alla pagina di partenza**, con i
+  suoi filtri, ricerca, ordinamento e pagina (aperta dal menu: come prima)
+- **Cartolina cartacea**: assegnando (anche il sorvegliante di gruppo) si può
+  spuntare *Ha chiesto la cartolina cartacea*. Il segno sta sull'assegnazione:
+  nell'elenco degli assegnati compare l'etichetta "cartaceo" e la pagina
+  **Cartacei** (menu, sotto *Assegnazioni*) elenca i territori cartacei fuori
+  e a chi, con i giorni e il pulsante Rientro. Al rientro escono dall'elenco
+
+### Richieste dal modulo pubblico
+- **Modulo pubblico** all'indirizzo `/richiesta`, senza login (l'indirizzo
+  completo è scritto nella Home, da passare ai proclamatori): nome e cognome,
+  *nuovo territorio* o *riconsegna*, una nota. Nella riconsegna il territorio
+  si sceglie con il **completamento automatico**: si scrive il numero o la
+  zona e compaiono i territori (attivi, o disattivati ma ancora fuori), con
+  numero e zona soltanto; si accetta solo un territorio dell'elenco. A parte
+  questo elenco il modulo non mostra nessun dato già presente: né nomi, né a
+  chi è assegnato un territorio o se lo è
+- **Contro lo spam**: un campo trappola nascosto, un tempo minimo fra apertura
+  e invio (in questi due casi risponde "inviata" senza salvare) e al massimo 5
+  richieste all'ora dallo stesso indirizzo
+- **Avviso per email** ad amministratori e assistenti (permesso
+  `richieste.gestisci`) con l'email confermata, se il server di posta
+  funziona; la richiesta resta comunque nella Home
+- **Nella Home**, riquadro *Richieste*: per un nuovo territorio i proclamatori
+  attivi con un nome simile a quello scritto (uguale, iniziale, una lettera
+  sbagliata, in qualsiasi ordine e senza accenti), ognuno porta al modulo
+  *Assegna* già con quel proclamatore; *Nessuno di questi* apre il modulo
+  vuoto. Per una riconsegna, a chi risulta assegnato il territorio e *Registra
+  rientro →*. Fatta l'assegnazione o il rientro, la richiesta risulta evasa;
+  altrimenti si può **scartare**
+- Nome e nota sono cifrati nel database e non vanno nel registro delle
+  attività; le richieste gestite si cancellano da sole dopo 90 giorni
+  (`richieste:pulizia`, ogni notte)
+
+### Gruppi di servizio
+- Li gestisce solo l'amministratore (menu *Gruppi di servizio*): nome,
+  **sorvegliante** (un proclamatore attivo), **membri** e **pacchetto** di
+  territori. Un proclamatore sta in un solo gruppo; il sorvegliante ne è
+  anche membro
+- Creando il gruppo il sorvegliante riceve un'**utenza** con un'**email
+  fittizia** creata dall'applicazione: iniziale del nome e cognome sul
+  dominio `termanager.it` (Francesco Fontana → `ffontana@termanager.it`; se
+  è già presa, un numero in coda), e una password temporanea. Si vedono una
+  volta sola; la password va cambiata al primo accesso (la pagina dice
+  "Password temporanea", non "Ripristino da backup"). L'email non si
+  chiede, non riceve posta e non va confermata. Due gruppi non possono avere
+  lo stesso nome. Se perde la password, l'amministratore ne genera un'altra
+  temporanea dalla pagina del gruppo o dal pannello *Utenti* ("Nuova password
+  temporanea" sulla riga del sorvegliante): si vede una volta sola, va
+  cambiata al primo accesso, e le sessioni aperte con quella vecchia si
+  chiudono
+- I territori del pacchetto si aggiungono in blocco tra quelli in reparto,
+  **in ordine di priorità** come "Da assegnare" nella Home (prima i
+  prioritari, poi quelli fermi da più tempo), con ricerca, filtri per zona,
+  tipologia e "solo prioritari", e "Seleziona tutti quelli mostrati".
+  Restano **"In gruppo …"**: non sono un'assegnazione (statistiche e medie non
+  cambiano), escono da "Da assegnare" e dalla pagina *Assegna*
+- Il sorvegliante entra e vede **solo "Il mio gruppo"** e il proprio profilo
+  (ogni altra pagina risponde 403): dà i territori ai membri — o a sé — e ne
+  nasce un'**assegnazione normale**, che conta come le altre ed è segnata
+  "via gruppo …"; poi manda il link (copia o condividi), registra i rientri,
+  apre la piantina e rimanda in reparto quelli non ancora dati. Il suo
+  pacchetto è in ordine di priorità (prima i da dare, prioritari in testa,
+  poi quelli già dati) e si filtra per stato, zona, tipologia e "solo
+  prioritari"; sotto il nome del gruppo compaiono nome e cognome del
+  sorvegliante. Toccando il numero di un territorio si apre l'**anteprima**
+  (la miniatura della piantina) con il collegamento al PDF
+- Al **rientro** il territorio torna in reparto ed esce dal pacchetto
+- **Sciogliere il gruppo** toglie il ruolo al sorvegliante e **elimina il
+  gruppo**, che non resta nello storico: i territori solo nel pacchetto
+  tornano in reparto, i membri si liberano e l'**utenza del sorvegliante si
+  elimina** (anche una sessione aperta si chiude): torna un proclamatore come
+  gli altri. Le assegnazioni che aveva fatto passano a chi scioglie il
+  gruppo; nel registro delle attività le sue voci restano a nome
+  "Sorvegliante del gruppo …". I territori già dati restano ai membri come
+  assegnazioni qualsiasi, che del gruppo conservano solo il nome ("via
+  gruppo …"). Per ripartire si crea un gruppo nuovo
+- **Un sorvegliante che non è più attivo scioglie il gruppo**, come togliergli
+  il ruolo: succede se lo si rende non attivo (dall'elenco o dalla modifica),
+  se lo si sposta nel cestino o lo si anonimizza. Prima di disattivarlo o
+  cestinarlo dall'elenco si chiede conferma; riattivarlo non ricostruisce il
+  gruppo. Un membro non attivo resta nel gruppo ma non riceve territori; nel
+  cestino esce dal gruppo
+- **Chi fa parte di un gruppo è segnalato**: badge "Gruppo …" o
+  "Sorvegliante del gruppo …" nell'elenco dei proclamatori (con il filtro
+  *In un gruppo di servizio*) e in testa alla scheda; nella scelta del
+  proclamatore (Assegna, Registro) la nota "gruppo …" accanto al nome, che
+  resta comunque sceglibile
+- **Dettagli del gruppo**: la scheda del proclamatore dice se è sorvegliante
+  (gruppo, membri, territori nel pacchetto e da dare, assegnazioni nate dal
+  gruppo, email per entrare, stato della password e ultimo accesso) o membro; il
+  sorvegliante ritrova gli stessi numeri nel suo
+  *Profilo*
 
 ### Campagne
 - CRUD con date di inizio e fine
@@ -561,6 +859,10 @@ docker compose --profile dev up -d --build
 ### Registro assegnazioni
 - Filtri per anno teocratico, zona, tipologia, stato e ricerca testuale
 - Colonne: territorio, proclamatore, date, giorni, campagna
+- **Modulo S-13 per email**: l'ultima domenica di ogni mese alle 8 il modulo
+  S-13 dell'anno di servizio in corso parte in PDF agli amministratori,
+  all'email della loro utenza se confermata (`registro:invia-s13`, anche a
+  mano). Non passa dalla coda: il PDF contiene i nomi dei proclamatori
 
 ### Audit log
 - Tracciamento automatico su tutti i modelli
@@ -568,9 +870,16 @@ docker compose --profile dev up -d --build
 - Filtri per utente e tipo evento, con diff prima/dopo
 - Pulizia automatica schedulata secondo la retention configurata
 
-### XML Exchange
+### Backup e import
+- **Backup completo `.zip`**: dati gestionali, utenti e file caricati (PDF
+  territori, miniature, logo) in un unico pacchetto scaricabile e ripristinabile
+- Barra di avanzamento reale su backup e ripristino (lavoro svolto, non tempo)
+- Ripristino da pacchetto, con cambio password obbligatorio per tutti gli utenti
+- **Zona pericolosa**: azzeramento completo con backup obbligatorio scaricato,
+  password dell'amministratore e conferma esplicita prima di procedere
+- Import ed export XML dell'intero set di dati gestionali (senza i file)
 - Conversione di dump SQL legacy in XML compatibile
-- Import ed export XML dell'intero set di dati gestionali
+- Import massivo dei PDF dei territori da cartella o archivio ZIP
 
 ### Zone e tipologie
 - Gestione inline: aggiungi, rinomina, attiva/disattiva, elimina
@@ -580,24 +889,33 @@ docker compose --profile dev up -d --build
 
 ## Ruoli e permessi
 
-Tre ruoli con permessi granulari (spatie/laravel-permission):
+Quattro ruoli con permessi granulari (spatie/laravel-permission):
 
-| Permesso              | Amministratore | Assistente | Operatore |
-|-----------------------|:--------------:|:----------:|:---------:|
-| `settings.manage`     | ✅ | | |
-| `territori.manage`    | ✅ | | |
-| `proclamatori.manage` | ✅ | ✅ | |
-| `campagne.manage`     | ✅ | ✅ | |
-| `registro.view`       | ✅ | ✅ | |
-| `registro.export`     | ✅ | | |
-| `territori.assign`    | ✅ | ✅ | ✅ |
-| `territori.return`    | ✅ | ✅ | ✅ |
-| `audit.view`          | ✅ | | |
-| `audit.export`        | ✅ | | |
+| Permesso              | Amministratore | Assistente | Operatore | Sorvegliante |
+|-----------------------|:--------------:|:----------:|:---------:|:------------:|
+| `settings.manage`     | ✅ | | | |
+| `territori.manage`    | ✅ | | | |
+| `proclamatori.manage` | ✅ | ✅ | | |
+| `campagne.manage`     | ✅ | ✅ | | |
+| `registro.view`       | ✅ | ✅ | | |
+| `registro.export`     | ✅ | | | |
+| `territori.assign`    | ✅ | ✅ | ✅ | |
+| `territori.return`    | ✅ | ✅ | ✅ | |
+| `audit.view`          | ✅ | | | |
+| `audit.export`        | ✅ | | | |
+| `richieste.gestisci`  | ✅ | ✅ | | |
+| `gruppo.gestisci`     | | | | ✅ |
 
 L'amministratore ha un bypass completo (`Gate::before` in `AppServiceProvider`).
 Il menu laterale mostra solo le voci per cui l'utente ha i permessi.
 
+Il ruolo **sorvegliante** non si assegna dalla pagina *Utenti*: nasce creando
+un gruppo di servizio e sparisce sciogliendolo. Della sua utenza, in *Utenti*,
+si può solo generare una nuova password temporanea (e aprire il gruppo). Chi ha solo quel ruolo è
+confinato da `LimitaSorvegliante` alla pagina del proprio gruppo, al rientro
+dei territori del gruppo e al profilo; le sue azioni ricontrollano che
+territorio e assegnazione siano del suo gruppo.
+
 I permessi sono verificati sia sulle rotte sia sulle richieste Livewire, quindi
 una revoca ha effetto immediato senza bisogno di ricaricare la pagina.
 
@@ -606,13 +924,14 @@ una revoca ha effetto immediato senza bisogno di ricaricare la pagina.
 ## Sicurezza e GDPR
 
 ### Sicurezza
-- **Cifratura a riposo**: nome e cognome dei proclamatori cifrati con AES-256-CBC
-  tramite `APP_KEY`
+- **Cifratura a riposo**: nome e cognome dei proclamatori cifrati con
+  AES-256-CBC tramite `APP_KEY`
 - **Password**: hash bcrypt
 - **RBAC**: middleware `permission:` sulle rotte, riapplicato anche alle
   richieste Livewire
 - **CSRF**: token su tutti i form
-- **Rate limiting**: sul login
+- **Rate limiting**: sul login e sul modulo pubblico delle richieste (5
+  all'ora per indirizzo, più campo trappola e tempo minimo contro lo spam)
 - **Host header**: accettate solo richieste il cui `Host` corrisponde a `APP_URL`
 - **Scheme forwarding**: lo schema è deciso dal server, non dall'header del
   client, per non falsare la validazione dei link firmati
@@ -621,15 +940,41 @@ una revoca ha effetto immediato senza bisogno di ricaricare la pagina.
 - **Sessioni**: in Redis, cookie httpOnly e `Secure` in produzione
 - **Esecuzione PHP**: solo `index.php` è un entrypoint valido; ogni altro `.php`
   restituisce 404
+- **Versione di PHP fissata alla patch** (`ARG PHP_VERSION` nel Dockerfile,
+  oggi 8.3.36 per CVE-2026-109618/109619): una build o prende quella versione
+  o fallisce, mai una base vecchia rimasta in cache. Va alzata a ogni rilascio
+  di sicurezza del ramo 8.3
+- **Sessioni native di PHP chiuse**: `session.upload_progress.enabled = 0` e
+  `session.use_strict_mode = 1` in `php.ini` (l'applicazione usa le sessioni
+  di Laravel; è la mitigazione indicata per le stesse CVE)
 
 ### GDPR
-- **Minimizzazione**: dei proclamatori si conservano solo nome, cognome e stato
+- **Informativa** (menu *Privacy*, solo amministratore): i valori che possono
+  cambiare — congregazione, conservazione del log, scadenza dei link,
+  download del PDF, server di posta, durata della sessione, indirizzo e HTTPS,
+  ruoli con i loro permessi, quanti dati sono conservati — si leggono al
+  momento da impostazioni e configurazione (`App\Livewire\Privacy`)
+- **Minimizzazione**: dei proclamatori si conservano solo nome, cognome e
+  stato. Niente telefono né email: il link lo manda chi assegna, scegliendo il
+  destinatario dai propri contatti, e l'app non vede quei contatti
 - **Cifratura a riposo**: i dati sono illeggibili anche con accesso diretto al DB
 - **Audit trail**: registro completo delle operazioni
 - **Diritto all'oblio**: funzione di anonimizzazione irreversibile
 - **Retention**: cancellazione automatica dei log oltre il periodo configurato
 - **No dati sensibili nei log**: l'audit registra gli identificativi, non i nomi
-  in chiaro
+  in chiaro (anche per l'utenza di un sorvegliante di gruppo, che porta il nome
+  di un proclamatore)
+- **Richieste dal modulo pubblico**: nome e nota cifrati come i dati dei
+  proclamatori, fuori dal registro delle attività e dalla coda (l'email di
+  avviso parte subito); cancellate 90 giorni dopo essere state gestite. Non
+  sono nei backup (né XML né `.zip`, che contiene lo stesso XML): sono
+  messaggi in arrivo, non dati gestionali, e un ripristino non le tocca.
+  L'azzeramento (*Zona pericolosa*) le cancella
+- **Email**: il modulo S-13 (con i nomi) va solo agli amministratori con
+  l'email confermata, l'avviso delle richieste solo a chi le gestisce
+- **Attenzione ai backup**: il pacchetto `.zip` e l'export XML contengono i dati
+  dei proclamatori **in chiaro** (l'export li legge decifrati). Vanno custoditi
+  in un luogo protetto e cancellati quando non servono
 
 ---
 
@@ -637,15 +982,17 @@ una revoca ha effetto immediato senza bisogno di ricaricare la pagina.
 
 | Tabella           | Descrizione                                                  |
 |-------------------|--------------------------------------------------------------|
-| `users`           | Utenti dell'applicazione                                     |
+| `users`           | Utenti; `password_change_required` blocca l'accesso finché non si sceglie una password nuova (`password_temporanea` dice se il motivo è una password provvisoria data dall'amministratore invece di un ripristino); `proclamatore_id` lega l'utenza del sorvegliante (email fittizia) al suo proclamatore; sciolto il gruppo l'utenza si elimina |
 | `settings`        | Configurazione singleton                                      |
 | `zone`            | Zone territoriali                                             |
 | `tipologie`       | Tipologie di territorio                                       |
-| `proclamatori`    | Assegnatari, con nome/cognome cifrati e soft delete           |
-| `territori`       | Cartoline con zona, tipologia, PDF, miniatura, soft delete    |
+| `proclamatori`    | Assegnatari, con nome/cognome cifrati e soft delete (niente contatti); `gruppo_servizio_id` è il gruppo di cui fanno parte |
+| `gruppi_servizio` | Gruppi di servizio attivi: nome (unico), sorvegliante. Sciolto, il gruppo si elimina |
+| `territori`       | Cartoline con zona, tipologia, PDF, miniatura, soft delete; `gruppo_servizio_id` se sono nel pacchetto di un gruppo |
 | `anni_teocratici` | Periodi settembre → agosto                                    |
 | `campagne`        | Periodi speciali con date e descrizione                       |
-| `assegnazioni`    | Territorio ↔ proclamatore, con date, anno e campagna          |
+| `assegnazioni`    | Territorio ↔ proclamatore, con date, anno e campagna; stato dell'invio del link (`link_sent`, `link_da_inviare`, `link_canale`); `gruppo_servizio_id` se data dal sorvegliante di un gruppo ancora attivo, `gruppo_nome` che resta anche dopo lo scioglimento; `cartaceo` se il proclamatore ha chiesto la cartolina cartacea |
+| `richieste`       | Richieste dal modulo pubblico: tipo (`nuovo`/`riconsegna`), nome e nota cifrati, numero del territorio, stato (`aperta`/`evasa`/`scartata`), l'assegnazione che l'ha evasa, chi e quando l'ha gestita |
 | `activity_log`    | Audit trail                                                   |
 
 **Vincoli e indici principali**
@@ -672,20 +1019,45 @@ Calcolato dinamicamente, non memorizzato:
 
 | Stato          | Condizione                                          |
 |----------------|-----------------------------------------------------|
-| `in_reparto`   | Attivo, nessuna assegnazione aperta                 |
+| `in_reparto`   | Attivo, nessuna assegnazione aperta, fuori dai pacchetti dei gruppi |
+| `in_gruppo`    | Nel pacchetto di un gruppo di servizio, non ancora dato a un membro |
 | `assegnato`    | Ha un'assegnazione con `returned_at` nullo          |
 | `da_rientrare` | Assegnato da più giorni della soglia configurata    |
 | `inattivo`     | Contrassegnato come non attivo                      |
 
 ### Priorità
-Un territorio è prioritario se lo è per **flag manuale** o perché non viene
-assegnato da più mesi della soglia configurata. La soglia automatica **vince
-sempre** sul flag: l'amministratore può aggiungere priorità, non toglierla
-quando la soglia è scattata.
+Un territorio è prioritario se lo è per **flag manuale** o perché è fermo
+(dall'ultimo rientro, o dalla creazione se mai assegnato) da più giorni della
+soglia configurata. La soglia automatica **vince sempre** sul flag:
+l'amministratore può aggiungere priorità, non toglierla quando la soglia è
+scattata. Assegnare il territorio azzera il flag.
+
+Dove si sceglie un territorio da dare — "Da assegnare" nella Home, l'aggiunta
+al pacchetto di un gruppo, "Il mio gruppo" — l'ordine è lo stesso: prima i
+prioritari, poi quelli fermi da più tempo, poi il numero
+(`Territorio::ordinaPerPriorita()`).
 
 ### Percentuale di percorrenza delle campagne
-- **Denominatore**: tutti i territori assegnati nel periodo della campagna
-- **Numeratore**: le assegnazioni contrassegnate come conteggiate
+- **Denominatore**: tutti i territori attivi
+- **Numeratore**: i territori attivi distinti con almeno un'assegnazione
+  collegata alla campagna e contrassegnata come conteggiata al rientro (un
+  territorio percorso due volte conta una volta sola)
+
+Al rientro la campagna viene proposta se il territorio era fuori almeno in
+parte del periodo: assegnato durante la campagna, rientrato durante la
+campagna, oppure fuori per tutta la sua durata. Se sia stato davvero percorso
+lo decide l'operatore con la spunta. Se più campagne corrispondono viene
+proposta la più recente. I territori assegnati durante la campagna e non
+ancora rientrati compaiono nel dettaglio come "in corso".
+
+### Gruppi di servizio e statistiche
+Mettere un territorio nel pacchetto di un gruppo **non** è un'assegnazione:
+non crea righe in `assegnazioni`, quindi non tocca medie, durate, percorrenza
+delle campagne né il registro. Conta solo quando il sorvegliante lo dà a un
+membro: da lì è un'assegnazione come le altre (con `gruppo_servizio_id` per
+sapere da dove viene). Il tempo passato nel pacchetto prima di essere dato non
+viene contato. La priorità automatica guarda l'ultima assegnazione, come
+sempre.
 
 ---
 
@@ -696,7 +1068,7 @@ quando la soglia è scattata.
 | Componente        | Tecnologia                                 |
 |-------------------|--------------------------------------------|
 | Framework         | Laravel 11                                 |
-| PHP               | 8.3 (FPM)                                  |
+| PHP               | 8.3 (FPM), versione fissata nel Dockerfile |
 | Interfaccia       | Livewire 3.5 + TailwindCSS 4 + Alpine.js   |
 | Database          | MariaDB 11                                 |
 | Cache/Sessioni/Code| Redis 7                                   |
@@ -711,13 +1083,16 @@ quando la soglia è scattata.
 ```
 TerManager2/
 ├── app/
-│   ├── Console/Commands/       # audit:cleanup, app:create-initial-admin
-│   ├── Http/Controllers/       # PDF pubblici, import, login
-│   ├── Jobs/                   # Import PDF massivo (in coda)
-│   ├── Livewire/               # Tutti i componenti di interfaccia
-│   ├── Models/                 # 9 modelli Eloquent
+│   ├── Console/Commands/       # audit:cleanup, backup:cleanup, app:create-initial-admin,
+│   │                           # utenti:conferma-email, territori:file-orfani
+│   ├── Http/Controllers/       # PDF pubblici, import, backup, login, cambio password
+│   ├── Http/Middleware/        # RequirePasswordChange, LimitaSorvegliante
+│   ├── Jobs/                   # Import PDF, backup, ripristino, azzeramento (in coda)
+│   ├── Livewire/               # Tutti i componenti di interfaccia (Gruppi/: gruppi di servizio)
+│   ├── Models/                 # 12 modelli Eloquent
 │   ├── Providers/              # AppServiceProvider
-│   └── Services/               # Miniature PDF, stato import
+│   └── Services/               # Miniature PDF, import, archivio backup, posta,
+│                               # piantine, modulo S-13, gruppi di servizio
 ├── bootstrap/app.php           # Middleware, proxy e host fidati
 ├── config/                     # Configurazione Laravel
 ├── database/
@@ -726,14 +1101,21 @@ TerManager2/
 ├── docker/
 │   ├── nginx/default.conf      # Vhost
 │   ├── php/
-│   │   ├── Dockerfile          # Build multi-stage
+│   │   ├── Dockerfile          # Build multi-stage (runtime = ultimo stage)
 │   │   ├── entrypoint.sh       # Avvio: chiave, migrazioni, cache
 │   │   ├── queue-entrypoint.sh # Avvio worker e scheduler
 │   │   ├── php.ini
 │   │   └── www.conf
 │   └── supervisor/             # nginx + php-fpm nello stesso container
-├── resources/                  # CSS, JS, viste Blade
+├── resources/
+│   ├── css/app.css             # Sistema di pulsanti, tabelle responsive, console
+│   ├── js/
+│   └── views/
+│       ├── components/btn.blade.php  # L'unico pulsante dell'applicazione
+│       └── livewire/           # Una vista per componente
 ├── routes/web.php              # Rotte con i relativi permessi
+├── tests/                      # Suite PHPUnit (profilo compose "test") e tests/js (Node)
+├── phpunit.xml                 # Configurazione e ambiente dei test
 ├── docker-compose.yml          # Unico, produzione e sviluppo
 ├── .env.example                # Tutta la configurazione
 ├── HANDOFF.md                  # Stato del progetto per chi subentra

app/Console/Commands/BackupCleanup.php

@@ -0,0 +1,96 @@
+<?php
+
+namespace App\Console\Commands;
+
+use Illuminate\Console\Command;
+
+/**
+ * Rimuove gli archivi di backup e i pacchetti caricati piu' vecchi di un
+ * giorno.
+ *
+ * Sono file grossi che vivono nel volume `storage_data`, lo stesso dei PDF dei
+ * territori: un download mai completato o un ripristino interrotto ne lascia
+ * uno indietro, e senza pulizia si accumulano finche' il volume non si riempie
+ * — a quel punto smettono di funzionare anche l'import dei PDF e i log.
+ *
+ * La creazione di un nuovo backup fa gia' la sua pulizia, ma solo se qualcuno
+ * ne crea uno: un'installazione che non tocca piu' la pagina resterebbe con i
+ * residui addosso per sempre. Da qui il task pianificato.
+ */
+class BackupCleanup extends Command
+{
+    protected $signature = 'backup:cleanup {--ore=24 : Eta minima, in ore, dei file da rimuovere}';
+
+    protected $description = 'Rimuove archivi di backup e pacchetti di ripristino piu\' vecchi di N ore';
+
+    /** Cartelle sotto storage/app in cui vivono i file temporanei del backup. */
+    private const CARTELLE = [
+        'backups' => '*.zip',
+        'backup-restore-in' => '*.zip',
+    ];
+
+    public function handle(): int
+    {
+        $ore = max(1, (int) $this->option('ore'));
+        $limite = now()->subHours($ore)->getTimestamp();
+
+        $rimossi = 0;
+        $liberati = 0;
+
+        foreach (self::CARTELLE as $cartella => $pattern) {
+            $percorso = storage_path('app/' . $cartella);
+
+            if (! is_dir($percorso)) {
+                continue;
+            }
+
+            foreach (glob($percorso . '/' . $pattern) ?: [] as $file) {
+                if (filemtime($file) >= $limite) {
+                    continue;
+                }
+
+                $dimensione = filesize($file) ?: 0;
+
+                if (@unlink($file)) {
+                    $rimossi++;
+                    $liberati += $dimensione;
+                }
+            }
+        }
+
+        // Le cartelle di staging del ripristino: il job le cancella nel
+        // finally, ma un processo ucciso a meta' non arriva a eseguirlo.
+        $staging = storage_path('app/backup-restore');
+        if (is_dir($staging)) {
+            foreach (glob($staging . '/*', GLOB_ONLYDIR) ?: [] as $dir) {
+                if (filemtime($dir) < $limite) {
+                    $this->rimuoviCartella($dir);
+                    $rimossi++;
+                }
+            }
+        }
+
+        $this->info(sprintf(
+            'Pulizia backup: %d elementi rimossi, %.1f MB liberati.',
+            $rimossi,
+            $liberati / 1048576
+        ));
+
+        return self::SUCCESS;
+    }
+
+    private function rimuoviCartella(string $path): void
+    {
+        $iterator = new \RecursiveIteratorIterator(
+            new \RecursiveDirectoryIterator($path, \FilesystemIterator::SKIP_DOTS),
+            \RecursiveIteratorIterator::CHILD_FIRST
+        );
+
+        foreach ($iterator as $item) {
+            /** @var \SplFileInfo $item */
+            $item->isDir() ? @rmdir($item->getPathname()) : @unlink($item->getPathname());
+        }
+
+        @rmdir($path);
+    }
+}

app/Console/Commands/ConfermaEmailUtente.php

@@ -0,0 +1,44 @@
+<?php
+
+namespace App\Console\Commands;
+
+use App\Models\User;
+use Illuminate\Console\Command;
+
+/**
+ * Conferma a mano l'email di un utente, dalla riga di comando.
+ *
+ * Per l'emergenza: la posta non funziona e nessun amministratore confermato
+ * può sistemarla (per esempio subito dopo l'aggiornamento che ha reso
+ * obbligatoria la conferma). Chi ha accesso al server è già fidato.
+ */
+class ConfermaEmailUtente extends Command
+{
+    protected $signature = 'utenti:conferma-email {email : Indirizzo dell\'utente da confermare}';
+
+    protected $description = 'Segna come confermata l\'email di un utente (emergenza: posta non funzionante)';
+
+    public function handle(): int
+    {
+        $user = User::where('email', $this->argument('email'))->first();
+
+        if (! $user) {
+            $this->error('Nessun utente con questo indirizzo.');
+
+            return self::FAILURE;
+        }
+
+        if ($user->hasVerifiedEmail()) {
+            $this->info("{$user->email} è già confermato.");
+
+            return self::SUCCESS;
+        }
+
+        $user->markEmailAsVerified();
+        activity()->performedOn($user)->log('email_confermata_da_riga_di_comando');
+
+        $this->info("Email di {$user->email} confermata.");
+
+        return self::SUCCESS;
+    }
+}

app/Console/Commands/CreateInitialAdmin.php

@@ -95,6 +95,11 @@ class CreateInitialAdmin extends Command
                 'password' => Hash::make($password),
             ]);
 
+            // Confermato da subito: su un'installazione nuova il server di
+            // posta non c'è ancora, e chi ha accesso alla riga di comando del
+            // server non ha bisogno di dimostrare di chi è l'indirizzo. Senza,
+            // il primo amministratore arriverebbe solo alla pagina della posta.
+            $user->markEmailAsVerified();
             $user->assignRole('amministratore');
 
             return $user;

app/Console/Commands/InviaModuloS13.php

@@ -0,0 +1,75 @@
+<?php
+
+namespace App\Console\Commands;
+
+use App\Mail\ModuloS13Mail;
+use App\Models\AnnoTeocratico;
+use App\Models\User;
+use App\Services\ConfigurazionePosta;
+use App\Services\Registro\ModuloS13;
+use Illuminate\Console\Command;
+use Illuminate\Support\Facades\Mail;
+
+/**
+ * Il modulo S-13 dell'anno di servizio in corso, per email agli
+ * amministratori (l'indirizzo della loro utenza, se confermato). Lo lancia lo
+ * scheduler l'ultima domenica di ogni mese (routes/console.php); a mano si
+ * può scegliere l'anno con --anno=2025-2026.
+ *
+ * Parte subito, non in coda: il PDF contiene i nomi dei proclamatori, che in
+ * coda starebbero in chiaro. Senza un server di posta funzionante non manda
+ * niente e lo dice.
+ */
+class InviaModuloS13 extends Command
+{
+    protected $signature = 'registro:invia-s13 {--anno= : etichetta dell\'anno di servizio, es. 2025-2026 (predefinito: quello in corso)}';
+
+    protected $description = 'Manda per email agli amministratori il modulo S-13 dell\'anno di servizio';
+
+    public function handle(ModuloS13 $modulo, ConfigurazionePosta $posta): int
+    {
+        if (! $posta->funzionante()) {
+            $this->warn('Nessun server di posta funzionante: modulo S-13 non inviato.');
+
+            return self::SUCCESS;
+        }
+
+        $anno = $this->option('anno')
+            ? AnnoTeocratico::where('label', $this->option('anno'))->first()
+            : AnnoTeocratico::corrente();
+        if (! $anno) {
+            $this->error("Anno di servizio {$this->option('anno')} non trovato.");
+
+            return self::FAILURE;
+        }
+
+        $destinatari = User::role('amministratore')->get()
+            ->filter(fn (User $u) => $u->email && $u->email_verified_at !== null)
+            ->values();
+        if ($destinatari->isEmpty()) {
+            $this->warn('Nessun amministratore con un\'email confermata: modulo S-13 non inviato.');
+
+            return self::SUCCESS;
+        }
+
+        $pdf = $modulo->genera($anno);
+
+        // Uno per uno: un indirizzo rifiutato non ferma gli altri.
+        $inviati = 0;
+        foreach ($destinatari as $utente) {
+            try {
+                Mail::to($utente->email)->send(new ModuloS13Mail($utente, $anno, $pdf));
+                $inviati++;
+            } catch (\Throwable $e) {
+                report($e);
+                $this->error("Invio a {$utente->email} non riuscito: {$e->getMessage()}");
+            }
+        }
+
+        // Nel registro quanti, non chi: gli indirizzi stanno nelle utenze.
+        activity()->withProperties(['anno' => $anno->label, 'destinatari' => $inviati])->log('s13_inviato');
+        $this->info("Modulo S-13 {$anno->label} inviato a {$inviati} amministratori su {$destinatari->count()}.");
+
+        return $inviati === $destinatari->count() ? self::SUCCESS : self::FAILURE;
+    }
+}

app/Console/Commands/PuliziaRichieste.php

@@ -0,0 +1,34 @@
+<?php
+
+namespace App\Console\Commands;
+
+use App\Models\Richiesta;
+use Illuminate\Console\Command;
+
+/**
+ * Le richieste dal modulo pubblico portano nome e note scritti da chi non ha
+ * un account: gestite (evase o scartate) servono ancora un po' per
+ * riferimento, poi si cancellano. Quelle aperte restano finché qualcuno non
+ * le gestisce.
+ */
+class PuliziaRichieste extends Command
+{
+    /** Dopo quanti giorni dalla gestione una richiesta si cancella. */
+    public const GIORNI = 90;
+
+    protected $signature = 'richieste:pulizia';
+
+    protected $description = 'Cancella le richieste del modulo pubblico gestite da più di ' . self::GIORNI . ' giorni';
+
+    public function handle(): int
+    {
+        $cancellate = Richiesta::query()
+            ->where('stato', '!=', Richiesta::APERTA)
+            ->where('gestita_at', '<', now()->subDays(self::GIORNI))
+            ->delete();
+
+        $this->info("Richieste cancellate: {$cancellate}");
+
+        return self::SUCCESS;
+    }
+}

app/Console/Commands/TerritoriFileOrfani.php

@@ -0,0 +1,79 @@
+<?php
+
+namespace App\Console\Commands;
+
+use App\Livewire\Settings\XmlExchange;
+use App\Models\Setting;
+use App\Models\TerritorioMappa;
+use Illuminate\Console\Command;
+use Illuminate\Support\Facades\Storage;
+
+/**
+ * Elenca (e su richiesta cancella) i file dei territori che nessuna riga usa.
+ *
+ * Fino all'ottobre 2026 l'import XML ricreava i territori con id nuovi senza
+ * toccare i loro file: PDF, miniature e versioni dei territori di prima
+ * restavano sul disco, e passavano da un backup all'altro perché l'archivio
+ * copia tutto il disco pubblico. Oggi l'import li elimina da sé; questo
+ * comando serve a ripulire quelli accumulati prima.
+ *
+ * Di default non cancella niente: elenca. Con --elimina cancella.
+ */
+class TerritoriFileOrfani extends Command
+{
+    protected $signature = 'territori:file-orfani {--elimina : Cancella i file trovati invece di elencarli}';
+
+    protected $description = 'Elenca (o cancella con --elimina) i file dei territori che nessuna riga usa più';
+
+    private const CARTELLE = ['territori-pdf', 'territori-thumbnails', 'territori-pdf-versioni', 'territori-mappe'];
+
+    public function handle(): int
+    {
+        $usati = array_flip(array_merge(
+            XmlExchange::fileDeiTerritori(),
+            array_filter([Setting::instance()->logo_path]),
+            TerritorioMappa::query()->whereNotNull('image_path')->pluck('image_path')->all(),
+        ));
+
+        $disco = Storage::disk('public');
+        $orfani = [];
+        $byte = 0;
+
+        foreach (self::CARTELLE as $cartella) {
+            foreach ($disco->files($cartella) as $file) {
+                if (! isset($usati[$file])) {
+                    $orfani[] = $file;
+                    $byte += $disco->size($file);
+                }
+            }
+        }
+
+        $peso = number_format($byte / 1048576, 1, ',', '.') . ' MB';
+
+        if ($orfani === []) {
+            $this->info('Nessun file orfano.');
+
+            return self::SUCCESS;
+        }
+
+        if (! $this->option('elimina')) {
+            foreach ($orfani as $file) {
+                $this->line($file);
+            }
+            $this->info(count($orfani) . " file orfani ({$peso}). Rilancia con --elimina per cancellarli.");
+
+            return self::SUCCESS;
+        }
+
+        $cancellati = 0;
+        foreach ($orfani as $file) {
+            if ($disco->delete($file)) {
+                $cancellati++;
+            }
+        }
+
+        $this->info("{$cancellati} file orfani cancellati ({$peso}).");
+
+        return self::SUCCESS;
+    }
+}

app/Http/Controllers/AssignmentPdfController.php

@@ -65,9 +65,11 @@ class AssignmentPdfController extends Controller
             return null;
         }
 
-        $ttlMonths = max(1, (int) \App\Models\Setting::getValue('assignment_link_ttl_hours', 1));
+        // Il link scade quando l'assegnazione raggiunge la soglia rientro
+        // (giorni_per_smarrito), cioè quando il territorio diventa "da rientrare".
+        $soglia = max(1, (int) \App\Models\Setting::getValue('giorni_per_smarrito', 120));
 
-        if ($assignment->assigned_at->copy()->addMonths($ttlMonths)->isPast()) {
+        if ($assignment->assigned_at->copy()->addDays($soglia)->isPast()) {
             return view('assignments.link-scaduto', [
                 'numero' => $assignment->territorio?->numero,
             ]);

app/Http/Controllers/Auth/LoginController.php

@@ -44,6 +44,11 @@ class LoginController extends Controller
         $request->session()->regenerate();
         activity()->causedBy(auth()->user())->log('login');
 
+        // Il sorvegliante di gruppo va dritto al suo gruppo.
+        if (Auth::user()->isSorvegliante() && Auth::user()->roles->count() === 1) {
+            return redirect()->route('mio-gruppo');
+        }
+
         return redirect()->intended(route('dashboard'));
     }
 }

app/Http/Controllers/Auth/PasswordChangeController.php

@@ -0,0 +1,100 @@
+<?php
+
+namespace App\Http\Controllers\Auth;
+
+use App\Http\Controllers\Controller;
+use App\Jobs\RestoreBackupArchive;
+use Illuminate\Http\Request;
+use Illuminate\Support\Facades\Cache;
+use Illuminate\Validation\Rules\Password;
+
+/**
+ * Cambio password obbligatorio, imposto dopo il ripristino di un backup o al
+ * primo accesso con una password temporanea data dall'amministratore
+ * (sorvegliante di gruppo): `password_temporanea` dice quale dei due.
+ *
+ * Volutamente NON e' un componente Livewire: la pagina deve restare
+ * raggiungibile mentre RequirePasswordChange respinge tutto il resto, incluse
+ * le richieste /livewire/update. Due rotte HTTP normali sono banali da
+ * escludere; distinguere quale componente sta dietro una POST di Livewire no.
+ */
+class PasswordChangeController extends Controller
+{
+    public function show()
+    {
+        $user = auth()->user();
+
+        return view('auth.password-change', [
+            'user' => $user,
+            // Chi arriva qui spontaneamente (dal profilo) puo' tornare indietro;
+            // chi e' stato dirottato dal middleware no.
+            'forced' => (bool) $user->password_change_required,
+            // Perché: una password temporanea, oppure un ripristino da backup.
+            'temporanea' => (bool) $user->password_temporanea,
+            // Il ripristino gira in coda e non ha una sessione in cui lasciare
+            // un flash; deposita l'esito in cache a nome di chi l'ha avviato e
+            // lo si legge qui, che e' la prima pagina che quella persona vede.
+            //
+            // Si legge senza consumare, e si cancella solo a password cambiata.
+            // Con un pull, il messaggio non arriverebbe mai a schermo: quando e'
+            // il middleware a dirottare una richiesta di Livewire, il client
+            // segue il 302 via fetch — ed e' quella fetch a bruciare il
+            // messaggio — per poi rifare la stessa GET con window.location, che
+            // troverebbe la cache gia' vuota.
+            'esitoRipristino' => Cache::get(RestoreBackupArchive::CHIAVE_ESITO . $user->id),
+        ]);
+    }
+
+    public function store(Request $request)
+    {
+        $user = $request->user();
+
+        // La password attuale si chiede solo a chi arriva qui di sua
+        // iniziativa, come fa il profilo.
+        //
+        // Dopo un ripristino no: gli hash sono quelli del backup, e la
+        // "password attuale" di un account e' quella che aveva all'epoca, che
+        // l'utente puo' benissimo non ricordare. Chiederla bloccherebbe fuori
+        // proprio le persone che questa schermata deve sbloccare; la garanzia li'
+        // e' la sessione. Fuori da quel caso, invece, bastava una sessione
+        // lasciata aperta per cambiare la password a qualcun altro e chiuderlo
+        // fuori dal suo account.
+        $regole = ['password' => ['required', 'confirmed', Password::min(8)]];
+        if (! $user->password_change_required) {
+            $regole['current_password'] = ['required', 'current_password'];
+        }
+
+        $validated = $request->validate($regole, [
+            'password.required' => 'Inserisci la nuova password.',
+            'password.confirmed' => 'Le due password non coincidono.',
+            'current_password.required' => 'Inserisci la password attuale.',
+            'current_password.current_password' => 'La password attuale non è corretta.',
+        ]);
+
+        // Il cast `hashed` sul modello cifra il valore al salvataggio.
+        $user->update([
+            'password' => $validated['password'],
+            'password_change_required' => false,
+            'password_temporanea' => false,
+        ]);
+
+        // La sessione corrente sopravvive al cambio, le altre no: dopo un
+        // ripristino le vecchie credenziali sono da considerarsi compromesse e
+        // una sessione aperta altrove lo e' altrettanto. Le altre le chiude
+        // AuthenticateSession (bootstrap/app.php) alla loro prossima richiesta,
+        // perche' l'hash della password e' cambiato; qui si cambia l'id di
+        // questa e si invalida il "ricordami".
+        $request->session()->regenerate();
+        $user->setRememberToken(null);
+        $user->save();
+
+        // L'esito del ripristino ha esaurito il suo scopo: e' stato letto, e la
+        // password richiesta e' stata impostata.
+        Cache::forget(RestoreBackupArchive::CHIAVE_ESITO . $user->id);
+
+        activity()->causedBy($user)->log('password changed');
+
+        return redirect()->route('dashboard')
+            ->with('success', 'Password aggiornata. Da ora accedi con quella nuova.');
+    }
+}

app/Http/Controllers/Auth/VerificaEmailController.php

@@ -0,0 +1,77 @@
+<?php
+
+namespace App\Http\Controllers\Auth;
+
+use App\Http\Controllers\Controller;
+use App\Models\User;
+use App\Services\ConfigurazionePosta;
+use Illuminate\Auth\Events\Verified;
+use Illuminate\Http\Request;
+use Illuminate\Support\Facades\Log;
+
+/**
+ * Conferma dell'indirizzo email degli utenti.
+ *
+ * Finché l'indirizzo non è confermato l'account non funziona: il middleware
+ * `verified` porta qui. Il link della mail funziona anche senza essere
+ * entrati: lo si apre spesso dal telefono, dove la sessione non c'è, e la
+ * firma dell'indirizzo (con scadenza) basta a garantire che venga dalla mail.
+ */
+class VerificaEmailController extends Controller
+{
+    public function avviso(Request $request, ConfigurazionePosta $posta)
+    {
+        if ($request->user()->hasVerifiedEmail()) {
+            return redirect()->route('dashboard');
+        }
+
+        return view('auth.verifica-email', [
+            'user' => $request->user(),
+            'postaFunzionante' => $posta->funzionante(),
+        ]);
+    }
+
+    public function invia(Request $request)
+    {
+        $user = $request->user();
+
+        if ($user->hasVerifiedEmail()) {
+            return redirect()->route('dashboard');
+        }
+
+        try {
+            $user->sendEmailVerificationNotification();
+        } catch (\Throwable $e) {
+            Log::warning('Email di conferma non inviata.', ['user' => $user->id, 'exception' => $e]);
+
+            return back()->with('error', 'L\'email non è partita: il server di posta non risponde o rifiuta l\'invio. Avvisa un amministratore.');
+        }
+
+        return back()->with('success', "Email inviata a {$user->email}. Apri il link che contiene (controlla anche lo spam).");
+    }
+
+    public function conferma(Request $request, int $id, string $hash)
+    {
+        $user = User::find($id);
+
+        // La firma garantisce id e scadenza; l'hash lega il link all'indirizzo
+        // di allora, così un link vecchio non conferma un'email cambiata dopo.
+        if (! $user || ! hash_equals(sha1($user->getEmailForVerification()), $hash)) {
+            abort(403, 'Link di conferma non valido.');
+        }
+
+        if (! $user->hasVerifiedEmail()) {
+            $user->markEmailAsVerified();
+            event(new Verified($user));
+            activity()->causedBy($user)->log('email_confermata');
+        }
+
+        $messaggio = 'Indirizzo email confermato.';
+
+        if ($request->user()?->is($user)) {
+            return redirect()->route('dashboard')->with('success', $messaggio);
+        }
+
+        return redirect()->route('login')->with('success', $messaggio . ' Ora puoi accedere.');
+    }
+}

app/Http/Controllers/Settings/BackupController.php

@@ -0,0 +1,162 @@
+<?php
+
+namespace App\Http\Controllers\Settings;
+
+use App\Http\Controllers\Controller;
+use App\Jobs\CreateBackupArchive;
+use App\Jobs\RestoreBackupArchive;
+use App\Services\BackupOperationState;
+use Illuminate\Http\Request;
+use Illuminate\Support\Str;
+
+/**
+ * Trasferimento dei file di backup: consegna dell'archivio prodotto e
+ * ricezione di quello da ripristinare.
+ *
+ * Non e' un componente Livewire come il resto della pagina: lo `streamDownload`
+ * di Livewire passa il file base64 dentro la risposta JSON, e un archivio con
+ * tutti i PDF dei territori non ci sta. L'avvio delle operazioni e la barra di
+ * avanzamento vivono invece in Livewire\Settings\BackupManager, che interroga
+ * BackupOperationState. Entrambe le rotte sono nel gruppo `settings.manage`.
+ */
+class BackupController extends Controller
+{
+    /**
+     * Tetto per il pacchetto in ingresso, in kilobyte.
+     *
+     * Deriva da `app.max_upload_mb`, da cui l'entrypoint ricava anche i limiti
+     * di nginx e di PHP. Il valore qui sta *sotto* quelli di un margine: se a
+     * fermare la richiesta e' nginx, il browser riceve un 413 senza corpo — o
+     * niente affatto — invece di un messaggio; se la ferma la validazione, chi
+     * carica legge cosa e' successo. Il margine copre anche l'intestazione
+     * multipart, che gonfia il corpo oltre la dimensione del file.
+     *
+     * La vista lo legge da qui per rifiutare il file prima ancora di iniziare a
+     * caricarlo: una sola fonte per un solo numero.
+     */
+    public static function maxUploadKb(): int
+    {
+        $mb = max(1, (int) config('app.max_upload_mb', 2048));
+
+        // 2% di margine, minimo 1 MB, per l'incapsulamento multipart.
+        return (int) (($mb - max(1, (int) ($mb * 0.02))) * 1000);
+    }
+
+    public static function maxUploadMb(): int
+    {
+        return (int) (self::maxUploadKb() / 1000);
+    }
+
+    public function __construct(
+        private readonly BackupOperationState $stato,
+    ) {
+    }
+
+    /**
+     * Consegna l'archivio prodotto da un'operazione di backup e annota che e'
+     * stato servito.
+     *
+     * L'annotazione e' meta' del blocco che protegge l'azzeramento: senza un
+     * `servito_at` il pulsante di conferma rifiuta di procedere, quindi non
+     * esiste una strada che cancelli i dati senza che l'archivio sia almeno
+     * uscito dal server. L'altra meta' e' la conferma umana in
+     * BackupManager::confermaAzzeramento().
+     *
+     * Il completamento del trasferimento *non* e' verificabile da qui: con
+     * `fastcgi_buffering on` (il default, e docker/nginx/default.conf non lo
+     * disattiva) nginx accetta l'intera risposta dal processo PHP e la inoltra
+     * per conto suo. PHP finisce di scrivere e prosegue anche se il browser ha
+     * chiuso la connessione al primo byte, quindi far scattare l'azzeramento
+     * "dopo l'ultimo byte" azzererebbe anche su un download annullato.
+     */
+    public function file(string $operationId)
+    {
+        $operazione = $this->stato->get($operationId);
+
+        abort_if($operazione === null, 404, 'Backup non piu\' disponibile: rigeneralo.');
+
+        $percorso = CreateBackupArchive::percorso($operationId);
+        abort_unless(is_file($percorso), 404, 'Archivio di backup non trovato: rigeneralo.');
+
+        $nome = $operazione['result']['nome_download'] ?? 'termanager2-backup.zip';
+
+        $this->stato->update($operationId, function (array $state) {
+            $state['result']['servito_at'] = now()->toDateTimeString();
+
+            return $state;
+        });
+
+        return response()
+            ->download($percorso, $nome, [
+                'Content-Type' => 'application/zip',
+                'Content-Length' => (string) filesize($percorso),
+            ]);
+    }
+
+    /**
+     * Riceve il pacchetto da ripristinare e mette in coda il lavoro.
+     *
+     * Risponde JSON perche' il form viene inviato via XMLHttpRequest: e' l'unico
+     * modo di avere una barra di caricamento reale sull'upload, che per un
+     * archivio di centinaia di MB e' la parte piu' lunga dell'operazione.
+     */
+    public function upload(Request $request)
+    {
+        $request->validate([
+            'backupZip' => ['required', 'file', 'mimes:zip', 'max:' . self::maxUploadKb()],
+        ], [
+            'backupZip.required' => 'Seleziona il pacchetto di backup da ripristinare.',
+            'backupZip.mimes' => 'Il pacchetto di backup deve essere un file .zip.',
+            'backupZip.max' => 'Il pacchetto supera i ' . self::maxUploadMb() . ' MB accettati dal server.',
+        ]);
+
+        $operationId = (string) Str::uuid();
+
+        // Stesso blocco del componente Livewire, ripetuto qui perche' questa e'
+        // una porta d'ingresso separata: un ripristino avviato mentre gira un
+        // azzeramento riscriverebbe le tabelle che l'altro sta cancellando.
+        // Il posto si prende subito e in un passo solo (occupa()): controllarlo
+        // e prenderlo solo dopo aver salvato il file lasciava una finestra in cui
+        // un import o un secondo ripristino passavano entrambi.
+        $inCorso = $this->stato->occupa($operationId, BackupOperationState::TIPO_RESTORE, 'In coda');
+        if ($inCorso !== null) {
+            return response()->json([
+                'message' => $this->stato->messaggioOccupato($inCorso),
+            ], 409);
+        }
+
+        try {
+            // Il file dell'upload vive in una cartella temporanea che sparisce a
+            // fine richiesta: il job lo troverebbe gia' cancellato.
+            $percorso = $request->file('backupZip')->storeAs(
+                'backup-restore-in',
+                $operationId . '.zip',
+                'local'
+            );
+        } catch (\Throwable $e) {
+            // Il posto e' gia' preso: senza chiuderlo resterebbe occupato da un
+            // ripristino che non partira' mai, per l'ora intera del TTL.
+            $this->stato->markFailed($operationId, 'Archivio non salvato sul server: ' . $e->getMessage());
+
+            throw $e;
+        }
+
+        if ($percorso === false) {
+            $this->stato->markFailed($operationId, 'Archivio non salvato sul server.');
+
+            return response()->json([
+                'message' => 'Il server non è riuscito a salvare il pacchetto ricevuto (spazio o permessi sul disco).',
+            ], 500);
+        }
+
+        $this->stato->log($operationId, 'Archivio ricevuto. In attesa del worker di coda.');
+
+        RestoreBackupArchive::dispatch(
+            $operationId,
+            storage_path('app/' . $percorso),
+            (int) auth()->id()
+        );
+
+        return response()->json(['operation_id' => $operationId]);
+    }
+}

app/Http/Controllers/Settings/PiantinaAnteprimaController.php

@@ -0,0 +1,33 @@
+<?php
+
+namespace App\Http\Controllers\Settings;
+
+use App\Http\Controllers\Controller;
+use App\Services\Piantine\PubblicazionePiantina;
+use Symfony\Component\HttpFoundation\Response;
+
+/**
+ * Il PDF dell'anteprima di una pubblicazione, da guardare prima di confermare.
+ *
+ * Lo prepara PubblicazionePiantina in una cartella privata: qui lo si serve
+ * soltanto, senza toccare il PDF in vigore del territorio. Il token è casuale
+ * e scade con l'anteprima; la rotta resta comunque riservata
+ * all'amministratore come il resto delle piantine.
+ */
+class PiantinaAnteprimaController extends Controller
+{
+    public function __invoke(string $token, PubblicazionePiantina $pubblicazione): Response
+    {
+        $percorso = $pubblicazione->pdfAnteprima($token);
+
+        abort_if($percorso === null, 404);
+
+        return response()->file($percorso, [
+            'Content-Type' => 'application/pdf',
+            // `inline`: si apre nel visualizzatore del browser invece di
+            // finire fra i download, che di un'anteprima non se ne fa niente.
+            'Content-Disposition' => 'inline; filename="anteprima-piantina.pdf"',
+            'Cache-Control' => 'no-store, max-age=0',
+        ]);
+    }
+}

app/Http/Controllers/Settings/XmlExchangeUploadController.php

@@ -4,10 +4,21 @@ namespace App\Http\Controllers\Settings;
 
 use App\Http\Controllers\Controller;
 use App\Livewire\Settings\XmlExchange;
+use App\Services\BackupOperationState;
 use Illuminate\Http\Request;
+use Illuminate\Support\Str;
 
 class XmlExchangeUploadController extends Controller
 {
+    /**
+     * Quanto resta occupato il posto unico se la richiesta di import muore senza
+     * liberarlo (timeout, errore fatale: casi in cui il `finally` non gira).
+     * L'import e' sincrono e PHP lo ferma comunque dopo max_execution_time
+     * (120 s): dieci minuti bastano a coprirlo, invece dell'ora intera pensata
+     * per i job in coda.
+     */
+    private const TTL_POSTO_IMPORT_XML = 600;
+
     public function convertSqlToXml(Request $request)
     {
         $request->validate([
@@ -51,13 +62,44 @@ class XmlExchangeUploadController extends Controller
             return back()->withErrors(['xmlImport' => 'File vuoto o non leggibile.']);
         }
 
-        $exchange = new XmlExchange();
-        $result = $exchange->importXmlFromContent($content);
+        // L'import svuota e riscrive le tabelle: non puo' girare insieme a un
+        // ripristino (che fa lo stesso), a un azzeramento, a un backup che le sta
+        // fotografando o a un import PDF che sta aggiornando i territori. Il
+        // ripristino chiama importXmlFromContent() per conto suo, gia' dentro il
+        // proprio posto: per questo il blocco sta qui, sulla porta d'ingresso, e
+        // non dentro l'import.
+        $stato = app(BackupOperationState::class);
+        $operationId = (string) Str::uuid();
+        $inCorso = $stato->occupa($operationId, BackupOperationState::TIPO_IMPORT_XML, 'Import XML', self::TTL_POSTO_IMPORT_XML);
+
+        if ($inCorso !== null) {
+            return back()->withErrors(['xmlImport' => $stato->messaggioOccupato($inCorso) . ' Nessun dato è stato modificato.']);
+        }
+
+        $stato->markRunning($operationId);
+
+        try {
+            $exchange = new XmlExchange();
+            $fileDiPrima = XmlExchange::fileDeiTerritori();
+            $result = $exchange->importXmlFromContent($content);
+
+            if (! isset($result['error'])) {
+                $result['stats']['file_rimossi'] = XmlExchange::eliminaFileNonPiuUsati($fileDiPrima);
+            }
+        } catch (\Throwable $e) {
+            $stato->markFailed($operationId, $e->getMessage());
+
+            throw $e;
+        }
 
         if (isset($result['error'])) {
+            $stato->markFailed($operationId, $result['error']);
+
             return back()->withErrors(['xmlImport' => $result['error']]);
         }
 
+        $stato->markCompleted($operationId);
+
         $stats = $result['stats'];
         $issues = $result['issues'];
 
@@ -65,6 +107,9 @@ class XmlExchangeUploadController extends Controller
         if (($stats['duplicate_territori'] ?? 0) > 0 || ($stats['assegnazioni_saltate'] ?? 0) > 0) {
             $message .= ' Territori duplicati saltati: ' . $stats['duplicate_territori'] . '. Assegnazioni saltate: ' . $stats['assegnazioni_saltate'] . '.';
         }
+        if (($stats['file_rimossi'] ?? 0) > 0) {
+            $message .= ' Eliminati ' . $stats['file_rimossi'] . ' file (PDF e miniature) dei territori sostituiti, che i dati importati non usano più.';
+        }
 
         return redirect()->route('xml.exchange')
             ->with('success', $message)

app/Http/Controllers/ShortPdfLinkController.php

@@ -15,10 +15,11 @@ class ShortPdfLinkController extends Controller
         abort_unless($assignment->is_aperta, 403);
         abort_unless($assignment->territorio?->pdf_path, 404);
 
-        // Unauthenticated users (proclamatori) are subject to link TTL
+        // Unauthenticated users (proclamatori) are subject to the link expiry:
+        // il link scade al raggiungimento della soglia rientro (giorni_per_smarrito).
         if (! auth()->check()) {
-            $ttlMonths = max(1, (int) \App\Models\Setting::getValue('assignment_link_ttl_hours', 1));
-            if ($assignment->assigned_at->copy()->addMonths($ttlMonths)->isPast()) {
+            $soglia = max(1, (int) \App\Models\Setting::getValue('giorni_per_smarrito', 120));
+            if ($assignment->assigned_at->copy()->addDays($soglia)->isPast()) {
                 return view('assignments.link-scaduto', [
                     'numero' => $assignment->territorio?->numero,
                 ]);

app/Http/Controllers/TerritorioFileController.php

@@ -0,0 +1,88 @@
+<?php
+
+namespace App\Http\Controllers;
+
+use App\Models\Territorio;
+use App\Models\TerritorioPdfVersione;
+use Illuminate\Support\Facades\Storage;
+use Symfony\Component\HttpFoundation\Response;
+
+/**
+ * PDF, miniature e versioni archiviate dei territori, solo per chi è dentro.
+ *
+ * I file stanno sul disco `public`, ma nginx non serve più le cartelle
+ * `territori-*` (docker/nginx/default.conf): prima chiunque scaricava
+ * /storage/territori-pdf/territorio-12-34.pdf senza login, con nomi facili da
+ * indovinare, e Cloudflare li teneva in cache pubblica per una settimana. I
+ * proclamatori continuano a riceverli dal link con codice e scadenza
+ * (AssignmentPdfController); da qui passano solo gli utenti autenticati, con i
+ * permessi della pagina che li mostra.
+ */
+class TerritorioFileController extends Controller
+{
+    public function pdf(Territorio $territorio): Response
+    {
+        return $this->servi($territorio->pdf_path, 'application/pdf', 'territorio-' . $territorio->numero . '.pdf');
+    }
+
+    /**
+     * Il PDF di un territorio del pacchetto, per il sorvegliante di gruppo:
+     * solo se il territorio è nel pacchetto del gruppo che sorveglia.
+     */
+    public function pdfGruppo(Territorio $territorio): Response
+    {
+        $this->delPacchetto($territorio);
+
+        return $this->pdf($territorio);
+    }
+
+    public function miniatura(Territorio $territorio): Response
+    {
+        return $this->servi($territorio->thumbnail_path, null, null);
+    }
+
+    /** La miniatura per l'anteprima in "Il mio gruppo", con la stessa regola del PDF. */
+    public function miniaturaGruppo(Territorio $territorio): Response
+    {
+        $this->delPacchetto($territorio);
+
+        return $this->miniatura($territorio);
+    }
+
+    /** Il territorio deve stare nel pacchetto del gruppo che l'utente sorveglia. */
+    private function delPacchetto(Territorio $territorio): void
+    {
+        $gruppo = auth()->user()->gruppoSorvegliato();
+        abort_unless($gruppo && $territorio->gruppo_servizio_id === $gruppo->id, 403);
+    }
+
+    public function versione(TerritorioPdfVersione $versione): Response
+    {
+        $numero = $versione->territorio?->numero ?? 'senza-territorio';
+
+        return $this->servi($versione->pdf_path, 'application/pdf', "territorio-{$numero}-versione-{$versione->id}.pdf");
+    }
+
+    private function servi(?string $percorso, ?string $tipo, ?string $nome): Response
+    {
+        $disco = Storage::disk('public');
+
+        abort_unless($percorso && $disco->exists($percorso), 404);
+
+        $intestazioni = [];
+        if ($tipo) {
+            $intestazioni['Content-Type'] = $tipo;
+        }
+        if ($nome) {
+            $intestazioni['Content-Disposition'] = 'inline; filename="' . $nome . '"';
+        }
+
+        // Privata: niente cache intermedie (Cloudflare). Va impostata dopo,
+        // perché BinaryFileResponse si dichiara pubblica da sola e
+        // sovrascriverebbe un Cache-Control passato fra le intestazioni.
+        // L'indirizzo porta l'impronta del percorso (?v=), che cambia col file.
+        return response()->file($disco->path($percorso), $intestazioni)
+            ->setPrivate()
+            ->setMaxAge(86400);
+    }
+}

app/Http/Middleware/LimitaSorvegliante.php

@@ -0,0 +1,58 @@
+<?php
+
+namespace App\Http\Middleware;
+
+use Closure;
+use Illuminate\Http\Request;
+use Symfony\Component\HttpFoundation\Response;
+
+/**
+ * Il sorvegliante di gruppo vede solo il proprio gruppo e il proprio
+ * profilo. La Home lo porta a "Il mio gruppo"; ogni altra pagina è 403,
+ * anche scrivendone l'indirizzo a mano. Le azioni Livewire passano: i
+ * componenti che può aprire controllano da sé che territori e assegnazioni
+ * siano del suo gruppo, e gli altri non può caricarli.
+ *
+ * Vale solo per chi ha il ruolo sorvegliante e nessun altro: un utente con
+ * anche un altro ruolo resta regolato dai permessi di quel ruolo. Sciolto il
+ * gruppo l'utenza si elimina: una sessione ancora aperta non ha più utente.
+ */
+class LimitaSorvegliante
+{
+    private const ROTTE_AMMESSE = [
+        'mio-gruppo',
+        'mio-gruppo.*',
+        'assegnazioni.rientra',
+        'profile',
+        'password.change',
+        'password.change.store',
+        'logout',
+        'verification.*',
+        // Le azioni Livewire: la rotta si chiama "default.livewire.update"
+        // (Livewire 3.7), non "livewire.update". Con 'livewire.*' ogni clic
+        // del sorvegliante finiva in 403.
+        '*livewire.*',
+    ];
+
+    public function handle(Request $request, Closure $next): Response
+    {
+        $user = $request->user();
+        if (! $user) {
+            return $next($request);
+        }
+
+        if (! $user->isSorvegliante() || $user->roles->count() > 1) {
+            return $next($request);
+        }
+
+        if ($request->routeIs(self::ROTTE_AMMESSE)) {
+            return $next($request);
+        }
+
+        if ($request->routeIs('dashboard')) {
+            return redirect()->route('mio-gruppo');
+        }
+
+        abort(403, 'Il sorvegliante di gruppo può usare solo la pagina del proprio gruppo.');
+    }
+}

app/Http/Middleware/RequirePasswordChange.php

@@ -0,0 +1,51 @@
+<?php
+
+namespace App\Http\Middleware;
+
+use Closure;
+use Illuminate\Http\Request;
+use Symfony\Component\HttpFoundation\Response;
+
+/**
+ * Chi ha `password_change_required` non puo' usare l'applicazione finche' non
+ * imposta una password nuova.
+ *
+ * Il flag lo accende il ripristino di un backup su TUTTI gli account: il
+ * pacchetto contiene gli hash delle password, quindi da quel momento nessuna
+ * delle vecchie e' piu' un segreto.
+ */
+class RequirePasswordChange
+{
+    /**
+     * Le sole rotte raggiungibili con il flag acceso: la schermata di cambio
+     * password, il suo invio e l'uscita. Tutto il resto — comprese le POST di
+     * Livewire, che altrimenti lascerebbero operare da una scheda gia' aperta —
+     * viene dirottato.
+     */
+    private const ROTTE_AMMESSE = [
+        'password.change',
+        'password.change.store',
+        'logout',
+        // Il link della mail di conferma: aperto in quel momento andrebbe
+        // perso, e la persona dovrebbe chiederne un altro.
+        'verification.verify',
+    ];
+
+    public function handle(Request $request, Closure $next): Response
+    {
+        $user = $request->user();
+
+        if (! $user || ! $user->password_change_required) {
+            return $next($request);
+        }
+
+        if ($request->routeIs(self::ROTTE_AMMESSE)) {
+            return $next($request);
+        }
+
+        // Vale anche per le POST di /livewire/update: il client segue la
+        // risposta redirezionata e porta la scheda sulla pagina di cambio
+        // password (vedi `response.redirected` in livewire.esm.js).
+        return redirect()->route('password.change');
+    }
+}

app/Jobs/CreateBackupArchive.php

@@ -0,0 +1,139 @@
+<?php
+
+namespace App\Jobs;
+
+use App\Livewire\Settings\XmlExchange;
+use App\Services\BackupArchive;
+use App\Services\BackupOperationState;
+use App\Services\Piantine\PiantineBackup;
+use Illuminate\Bus\Queueable;
+use Illuminate\Contracts\Queue\ShouldQueue;
+use Illuminate\Foundation\Bus\Dispatchable;
+use Illuminate\Queue\InteractsWithQueue;
+use Illuminate\Queue\SerializesModels;
+use Illuminate\Support\Facades\Log;
+
+/**
+ * Costruisce il pacchetto di backup in coda.
+ *
+ * In coda e non nella richiesta perche' un'installazione con qualche centinaio
+ * di PDF supera comodamente i 300 secondi di `fastcgi_read_timeout`: il browser
+ * si vedrebbe chiudere la connessione a meta' compressione, senza modo di
+ * distinguerlo da un errore.
+ */
+class CreateBackupArchive implements ShouldQueue
+{
+    use Dispatchable;
+    use InteractsWithQueue;
+    use Queueable;
+    use SerializesModels;
+
+    public int $tries = 1;
+
+    /** Sotto il --timeout=600 del worker: se sfora, e' il worker a ucciderlo. */
+    public int $timeout = 570;
+
+    /**
+     * @param  bool  $perAzzeramento  Quando true il job non chiude l'operazione
+     *                                ma la lascia in attesa del download: e'
+     *                                l'azzeramento che aspetta di avere
+     *                                l'archivio al sicuro prima di partire.
+     */
+    public function __construct(
+        public string $operationId,
+        public bool $perAzzeramento = false,
+    ) {
+    }
+
+    public function handle(BackupOperationState $stato, BackupArchive $archivio, XmlExchange $exchange, PiantineBackup $piantine): void
+    {
+        $stato->markRunning($this->operationId);
+        $stato->fase($this->operationId, 'Lettura dei dati gestionali');
+
+        $destinazione = self::percorso($this->operationId);
+
+        try {
+            $this->rimuoviArchiviVecchi($archivio);
+
+            $xml = $exchange->currentXmlBackup();
+            $datiPiantine = $piantine->esporta();
+
+            $stato->fase($this->operationId, 'Compressione dei file');
+
+            $archivio->create(
+                $xml,
+                $datiPiantine,
+                $destinazione,
+                fn (int $fatti, int $totale) => $stato->avanza($this->operationId, $fatti, $totale)
+            );
+        } catch (\Throwable $e) {
+            Log::error('Creazione del backup non riuscita.', ['exception' => $e]);
+            $stato->markFailed($this->operationId, $e->getMessage());
+
+            return;
+        }
+
+        $risultato = [
+            'file' => basename($destinazione),
+            'nome_download' => 'termanager2-backup-' . now()->format('Ymd-His') . '.zip',
+            'dimensione' => filesize($destinazione) ?: 0,
+        ];
+
+        if ($this->perAzzeramento) {
+            $stato->log($this->operationId, 'Archivio pronto. In attesa che il download sia completato.');
+            $stato->markAttesaDownload($this->operationId, $risultato);
+
+            return;
+        }
+
+        $stato->log($this->operationId, 'Backup pronto per il download.');
+        $stato->markCompleted($this->operationId, $risultato);
+    }
+
+    /**
+     * Chiamato da Laravel quando il job muore per cause che handle() non puo'
+     * intercettare: il timeout del worker (che uccide il processo), un errore
+     * fatale, una dipendenza non risolvibile.
+     *
+     * Senza, l'operazione resterebbe "in corso" e terrebbe occupato il posto
+     * unico fino alla scadenza del puntatore: un'ora in cui nessuno puo'
+     * avviare un backup e la pagina mostra una barra che non avanzera' mai.
+     */
+    public function failed(?\Throwable $e): void
+    {
+        app(BackupOperationState::class)->markFailed(
+            $this->operationId,
+            $e?->getMessage() ?: 'Creazione del backup interrotta (timeout o errore del worker).'
+        );
+
+        @unlink(self::percorso($this->operationId));
+    }
+
+    public static function percorso(string $operationId): string
+    {
+        return storage_path('app/backups/' . $operationId . '.zip');
+    }
+
+    /**
+     * Gli archivi restano su disco finche' il browser non li scarica, quindi un
+     * download mai completato lascerebbe un file per sempre. Si ripulisce
+     * all'inizio di ogni nuovo backup invece di aggiungere un task pianificato:
+     * il momento in cui serve spazio e' esattamente questo.
+     */
+    private function rimuoviArchiviVecchi(BackupArchive $archivio): void
+    {
+        $cartella = storage_path('app/backups');
+
+        if (! is_dir($cartella)) {
+            return;
+        }
+
+        $limite = now()->subDay()->getTimestamp();
+
+        foreach (glob($cartella . '/*.zip') ?: [] as $file) {
+            if (filemtime($file) < $limite) {
+                @unlink($file);
+            }
+        }
+    }
+}

app/Jobs/ImportTerritoryPdfFolder.php

@@ -4,6 +4,8 @@ namespace App\Jobs;
 
 use App\Models\Territorio;
 use App\Models\User;
+use App\Services\BackupOperationState;
+use App\Services\Piantine\PiantinaPdfService;
 use App\Services\TerritorioPdfImportState;
 use App\Services\TerritorioThumbnailService;
 use Illuminate\Bus\Queueable;
@@ -35,14 +37,21 @@ class ImportTerritoryPdfFolder implements ShouldQueue
     ) {
     }
 
-    public function handle(TerritorioPdfImportState $stateService, TerritorioThumbnailService $thumbnailService): void
+    public function handle(TerritorioPdfImportState $stateService, TerritorioThumbnailService $thumbnailService, BackupOperationState $postoUnico, PiantinaPdfService $pdfService): void
     {
         $stateService->markRunning($this->importId);
+        $postoUnico->markRunning($this->importId);
         $stateService->appendLog($this->importId, 'Worker avviato. Inizio elaborazione dei PDF.');
 
+        // Una chiave puo' raccogliere piu' territori ("12B" e "12 B"): non si
+        // tiene l'ultimo arrivato, si tengono tutti, cosi' l'abbinamento li vede
+        // e scarta il file come ambiguo invece di sceglierne uno a caso.
         $territoriMap = [];
         foreach (Territorio::withTrashed()->get() as $territorio) {
-            $territoriMap[$this->normalizeTerritoryNumber($territorio->numero)] = $territorio;
+            $chiave = $this->chiaveTerritorio((string) $territorio->numero);
+            if ($chiave !== '') {
+                $territoriMap[$chiave][] = $territorio;
+            }
         }
 
         $actor = User::find($this->actorId);
@@ -78,9 +87,26 @@ class ImportTerritoryPdfFolder implements ShouldQueue
                     continue;
                 }
 
-                $normalizedNumber = $territoryMatch['normalized_number'];
+                if (($territoryMatch['type'] ?? 'single') === 'unknown-suffix') {
+                    $codici = implode(', ', $territoryMatch['codes']);
+                    $esistenti = implode(', ', $territoryMatch['matched_numbers']);
+                    $stateService->increment($this->importId, 'skipped');
+                    $stateService->appendLog($this->importId, '[SKIP] ' . $originalName . ' - il nome indica il territorio ' . $codici . ', che non esiste (esiste ' . $esistenti . '): file non associato, per non sostituire il PDF di un altro territorio.');
+                    $stateService->addIssue($this->importId, [
+                        'file' => $originalName,
+                        'type' => 'unknown-suffix',
+                        'message' => 'Il nome indica il territorio ' . $codici . ', che non esiste: non associato a ' . $esistenti . '.',
+                        'matched_numbers' => $territoryMatch['matched_numbers'],
+                    ]);
+                    continue;
+                }
+
                 $matchedNumber = $territoryMatch['matched_number'];
                 $territorio = $territoryMatch['territorio'];
+                // Per id, non per numero: due file che nominano lo stesso
+                // territorio scritto in due modi ("12B.pdf", "12 B.pdf") sono
+                // comunque un doppione.
+                $normalizedNumber = $territorio->id;
 
                 if (isset($seenNumbers[$normalizedNumber])) {
                     $stateService->increment($this->importId, 'skipped');
@@ -111,24 +137,27 @@ class ImportTerritoryPdfFolder implements ShouldQueue
                 }
 
                 try {
-                    if ($territorio->pdf_path) {
-                        Storage::disk('public')->delete($territorio->pdf_path);
-                    }
-
-                    if ($territorio->thumbnail_path) {
-                        $thumbnailService->delete($territorio->thumbnail_path);
-                    }
-
                     // The territory id is part of the filename because the slug
                     // alone is not unique: "1 A" and "1-A" are distinct
                     // territory numbers that both slug to "territorio-1-a".
                     // Without it the second import overwrites the first's PDF
                     // and both rows point at one file — then removing the PDF
                     // from either territory breaks the other.
+                    //
+                    // Il nuovo file si scrive per primo, con un nome che non
+                    // coincide con quello in vigore; solo dopo il vecchio va
+                    // nello storico, come per le piantine. Prima si cancellava
+                    // il vecchio e poi si scriveva: con una scrittura fallita il
+                    // territorio restava senza PDF, e un import sbagliato non si
+                    // poteva annullare.
                     $storedFilename = Str::slug('territorio-' . $territorio->numero)
-                        . '-' . $territorio->id . '.pdf';
+                        . '-' . $territorio->id . '-' . now()->format('YmdHis') . '.pdf';
                     $publicPath = 'territori-pdf/' . $storedFilename;
-                    Storage::disk('public')->put($publicPath, file_get_contents($sourcePath));
+                    if (! Storage::disk('public')->put($publicPath, file_get_contents($sourcePath))) {
+                        throw new \RuntimeException('impossibile scrivere il file sul disco: il PDF in vigore non è stato toccato.');
+                    }
+
+                    $pdfService->archiviaCorrente($territorio, 'import');
                     $thumbnailPath = $thumbnailService->generate($publicPath);
 
                     $territorio->update([
@@ -166,10 +195,12 @@ class ImportTerritoryPdfFolder implements ShouldQueue
 
             $stateService->appendLog($this->importId, 'Import completato.');
             $stateService->markCompleted($this->importId);
+            $postoUnico->markCompleted($this->importId);
         } catch (\Throwable $exception) {
             $stateService->increment($this->importId, 'errors');
             $stateService->appendLog($this->importId, '[ERR] Errore fatale del job: ' . $exception->getMessage());
             $stateService->markFailed($this->importId);
+            $postoUnico->markFailed($this->importId, $exception->getMessage());
 
             throw $exception;
         } finally {
@@ -183,6 +214,10 @@ class ImportTerritoryPdfFolder implements ShouldQueue
      * Without this the import state is stranded in "running" — the UI polls it
      * until the 24h cache entry expires — and the uploaded temp directory is
      * never reclaimed, since handle()'s finally never executes.
+     *
+     * Libera anche il posto unico: senza, un import ucciso dal timeout
+     * lascerebbe backup, ripristino e azzeramento bloccati per l'ora intera
+     * del TTL, con un'operazione che non avanza piu'.
      */
     public function failed(?\Throwable $exception): void
     {
@@ -193,79 +228,128 @@ class ImportTerritoryPdfFolder implements ShouldQueue
             '[ERR] Job terminato senza completare: ' . ($exception?->getMessage() ?? 'timeout')
         );
         $stateService->markFailed($this->importId);
+        app(BackupOperationState::class)->markFailed(
+            $this->importId,
+            'Import PDF terminato senza completare: ' . ($exception?->getMessage() ?? 'timeout')
+        );
 
         Storage::disk('local')->deleteDirectory('bulk-territori-imports/' . $this->importId);
     }
 
+    /**
+     * Abbina il nome di un file al territorio, oppure spiega perche' non lo fa.
+     *
+     * La regola: nel nome si cercano i "numeri di territorio", cioe' cifre
+     * seguite al massimo da UNA lettera, attaccata o separata da uno spazio, un
+     * trattino, un trattino basso o un punto ("12", "012", "12B", "12 B",
+     * "12-b"). Le forme scritte in modo diverso dello stesso numero sono lo
+     * stesso numero: "12 B", "12B" e "12-B" sono tutte 12B, mai 12. Il numero
+     * deve stare da solo — "T12" o "12AB" non contano — e quelli che non
+     * corrispondono a nessun territorio (un anno, un CAP) vengono ignorati.
+     *
+     * Prima bastava che il numero di un territorio *comparisse* nel nome: "1-A"
+     * conteneva "1", e in assenza di un territorio 1A il PDF finiva sul
+     * territorio 1, sostituendone la mappa senza avvisare. Adesso una lettera
+     * dopo il numero fa parte del numero, e se quel territorio non esiste il
+     * file si scarta: si nomina il territorio 1 nel messaggio, ma non lo si
+     * tocca.
+     *
+     * Il file si scarta anche quando l'abbinamento non e' univoco: due numeri
+     * di territori esistenti nello stesso nome, o due territori che si
+     * scrivono diversi ma sono lo stesso numero ("12B" e "12 B"). Sostituire
+     * la mappa sbagliata e' peggio che non sostituirne nessuna: un file
+     * scartato si ricarica, un PDF sovrascritto non torna.
+     *
+     * I territori con numeri di altra forma (lettere davanti, piu' lettere in
+     * fondo) non si abbinano da nome file: il PDF va caricato dalla loro
+     * scheda.
+     */
     protected function resolveTerritoryFromFilename(string $filename, array $territoriMap): ?array
     {
-        if ($territoriMap === []) {
-            return null;
-        }
+        $trovati = [];
+        $suffissiSconosciuti = [];
 
-        $basename = pathinfo($filename, PATHINFO_FILENAME);
-        $normalizedBasename = mb_strtoupper($basename);
-        $normalizedBasename = preg_replace('/[^A-Z0-9]+/u', ' ', $normalizedBasename);
-        $normalizedBasename = trim(preg_replace('/\s+/', ' ', $normalizedBasename));
+        foreach ($this->numeriNelNomeFile($filename) as $codice) {
+            if (isset($territoriMap[$codice])) {
+                foreach ($territoriMap[$codice] as $territorio) {
+                    $trovati[$territorio->id] = $territorio;
+                }
 
-        $territoryKeys = array_keys($territoriMap);
-        usort($territoryKeys, function (string $left, string $right) {
-            $lengthComparison = mb_strlen($right) <=> mb_strlen($left);
-
-            if ($lengthComparison !== 0) {
-                return $lengthComparison;
-            }
-
-            return strnatcasecmp($left, $right);
-        });
-
-        $matches = [];
-
-        foreach ($territoryKeys as $normalizedNumber) {
-            if (! $this->filenameContainsTerritoryNumber($normalizedBasename, $normalizedNumber)) {
                 continue;
             }
 
-            $matches[] = [
-                'normalized_number' => $normalizedNumber,
-                'matched_number' => $territoriMap[$normalizedNumber]->numero,
-                'territorio' => $territoriMap[$normalizedNumber],
+            // "1A" che non esiste, mentre 1 si': e' il caso che prima
+            // sovrascriveva il territorio 1. Lo si annota per spiegarlo.
+            $base = preg_replace('/\p{L}$/u', '', $codice);
+            if ($base !== $codice && isset($territoriMap[$base])) {
+                $suffissiSconosciuti[$codice] = $territoriMap[$base];
+            }
+        }
+
+        $numeri = fn (array $territori) => array_values(array_unique(array_map(fn (Territorio $t) => $t->numero, $territori)));
+
+        if (count($trovati) > 1 || ($trovati !== [] && $suffissiSconosciuti !== [])) {
+            return [
+                'type' => 'ambiguous',
+                'matched_numbers' => $numeri(array_merge(array_values($trovati), ...array_values($suffissiSconosciuti))),
             ];
         }
 
-        if ($matches === []) {
+        if ($trovati === [] && $suffissiSconosciuti !== []) {
+            return [
+                'type' => 'unknown-suffix',
+                'codes' => array_keys($suffissiSconosciuti),
+                'matched_numbers' => $numeri(array_merge(...array_values($suffissiSconosciuti))),
+            ];
+        }
+
+        if ($trovati === []) {
             return null;
         }
 
-        if (count($matches) > 1) {
-            return [
-                'type' => 'ambiguous',
-                'matched_numbers' => array_values(array_map(fn(array $match) => $match['matched_number'], $matches)),
-            ];
-        }
+        $territorio = reset($trovati);
 
-        return $matches[0];
+        return [
+            'type' => 'single',
+            'normalized_number' => $this->chiaveTerritorio($territorio->numero),
+            'matched_number' => $territorio->numero,
+            'territorio' => $territorio,
+        ];
     }
 
-    protected function filenameContainsTerritoryNumber(string $normalizedBasename, string $normalizedNumber): bool
+    /**
+     * I numeri di territorio presenti nel nome del file, gia' nella forma di
+     * chiaveTerritorio(). Vedi la regola in resolveTerritoryFromFilename().
+     *
+     * @return array<int, string>
+     */
+    protected function numeriNelNomeFile(string $filename): array
     {
-        $escapedNumber = preg_quote($normalizedNumber, '/');
+        $nome = mb_strtoupper(pathinfo($filename, PATHINFO_FILENAME));
 
-        if (preg_match('/^\d+$/', $normalizedNumber)) {
-            $escapedNumber = '0*' . preg_quote(ltrim($normalizedNumber, '0') ?: '0', '/');
+        // Il lookahead finale e' quello che separa "12 B" (numero 12B) da
+        // "12 Via Roma" (numero 12): la lettera vale come parte del numero solo
+        // se dopo di lei la parola finisce.
+        preg_match_all('/(?<![\p{L}\p{N}])(\d+)(?:[ _.\-]?(\p{L}))?(?![\p{L}\p{N}])/u', $nome, $trovati, PREG_SET_ORDER);
+
+        $codici = [];
+        foreach ($trovati as $trovato) {
+            $codici[] = (ltrim($trovato[1], '0') ?: '0') . ($trovato[2] ?? '');
         }
 
-        return (bool) preg_match('/(^| )' . $escapedNumber . '(?= |$)/', $normalizedBasename);
+        return array_values(array_unique($codici));
     }
 
-    protected function normalizeTerritoryNumber(string $number): string
+    /**
+     * Forma di confronto di un numero di territorio: maiuscolo, senza
+     * separatori, senza zeri iniziali. "12 B", "12-b" e "012B" diventano tutti
+     * "12B"; due territori con la stessa chiave rendono ambiguo ogni file che
+     * la nomina.
+     */
+    protected function chiaveTerritorio(string $numero): string
     {
-        $normalized = preg_replace('/\s+/', ' ', trim(mb_strtoupper($number)));
+        $chiave = preg_replace('/[^\p{L}\p{N}]+/u', '', mb_strtoupper($numero));
 
-        if ($normalized !== '' && preg_match('/^\d+$/', $normalized)) {
-            return ltrim($normalized, '0') ?: '0';
-        }
-
-        return $normalized;
+        return preg_replace('/(?<!\d)0+(?=\d)/', '', $chiave);
     }
 }

app/Jobs/PreparaAnteprimaPiantina.php

@@ -0,0 +1,44 @@
+<?php
+
+namespace App\Jobs;
+
+use App\Services\Piantine\PubblicazionePiantina;
+use Illuminate\Bus\Queueable;
+use Illuminate\Contracts\Queue\ShouldQueue;
+use Illuminate\Foundation\Bus\Dispatchable;
+use Illuminate\Queue\InteractsWithQueue;
+use Illuminate\Queue\SerializesModels;
+
+/**
+ * Prepara l'anteprima di una pubblicazione (immagine HD + PDF) fuori dalla
+ * richiesta web. Non modifica niente: lo fa solo la conferma.
+ */
+class PreparaAnteprimaPiantina implements ShouldQueue
+{
+    use Dispatchable, InteractsWithQueue, Queueable, SerializesModels;
+
+    /** Ripetere non serve: un errore va mostrato, e si riprova dal pulsante. */
+    public int $tries = 1;
+
+    /** Il rendering più il margine per comporre il PDF. */
+    public int $timeout;
+
+    public function __construct(public string $token)
+    {
+        $this->timeout = (int) config('piantine.renderer_timeout') + 60;
+    }
+
+    public function handle(PubblicazionePiantina $pubblicazione): void
+    {
+        $pubblicazione->prepara($this->token);
+    }
+
+    /** Job ucciso (timeout, worker fermato): l'anteprima non resta "in corso" per sempre. */
+    public function failed(?\Throwable $e): void
+    {
+        app(PubblicazionePiantina::class)->segnaErrore(
+            $this->token,
+            'La preparazione dell\'anteprima si è interrotta. Riprova.'
+        );
+    }
+}

app/Jobs/ResetApplication.php

@@ -0,0 +1,208 @@
+<?php
+
+namespace App\Jobs;
+
+use App\Models\AnnoTeocratico;
+use App\Models\Assegnazione;
+use App\Models\Campagna;
+use App\Models\GruppoServizio;
+use App\Models\Proclamatore;
+use App\Models\Richiesta;
+use App\Models\Setting;
+use App\Models\Territorio;
+use App\Models\TerritorioMappa;
+use App\Models\TerritorioPdfVersione;
+use App\Models\Tipologia;
+use App\Models\User;
+use App\Models\Zona;
+use App\Services\BackupArchive;
+use App\Services\BackupOperationState;
+use Database\Seeders\RolesAndPermissionsSeeder;
+use Illuminate\Bus\Queueable;
+use Illuminate\Contracts\Queue\ShouldQueue;
+use Illuminate\Foundation\Bus\Dispatchable;
+use Illuminate\Queue\InteractsWithQueue;
+use Illuminate\Queue\SerializesModels;
+use Illuminate\Support\Facades\DB;
+use Illuminate\Support\Facades\Log;
+use Illuminate\Support\Facades\Storage;
+
+/**
+ * Riporta l'installazione allo stato di primo avvio: nessun dato gestionale,
+ * nessun file caricato, impostazioni ai valori di default, ruoli e permessi
+ * riseminati.
+ *
+ * Non e' reversibile e non fa backup da solo: parte solo dopo che l'archivio
+ * generato da CreateBackupArchive risulta scaricato per intero (vedi
+ * BackupController::file), cosi' non esiste una via che azzeri senza che una
+ * copia sia gia' al sicuro sul computer di chi ha premuto il pulsante.
+ */
+class ResetApplication implements ShouldQueue
+{
+    use Dispatchable;
+    use InteractsWithQueue;
+    use Queueable;
+    use SerializesModels;
+
+    public int $tries = 1;
+
+    public int $timeout = 570;
+
+    /**
+     * @param  int  $actorId  L'amministratore che ha chiesto l'azzeramento.
+     *                        E' l'unico account che sopravvive: un'installazione
+     *                        appena creata ha un amministratore, e cancellarli
+     *                        tutti lascerebbe l'applicazione senza nessuno che
+     *                        possa accedere fino al riavvio del container.
+     */
+    public function __construct(
+        public string $operationId,
+        public int $actorId,
+    ) {
+    }
+
+    public function handle(BackupOperationState $stato, BackupArchive $archivio): void
+    {
+        $stato->markRunning($this->operationId);
+
+        try {
+            // I file per primi, prima di toccare il database: svuotare il disco
+            // e' l'unico passo che puo' fallire per cause esterne (permessi sul
+            // volume), e fallire qui non ha ancora cancellato niente. Nell'ordine
+            // inverso un errore sui file lascerebbe un'applicazione con il
+            // database azzerato e il disco pieno di PDF che non appartengono
+            // piu' a nessun territorio.
+            $stato->fase($this->operationId, 'Cancellazione dei file caricati', 1);
+            $fileRimossi = $archivio->svuotaDiscoPubblico();
+            $stato->avanza($this->operationId, 1);
+            $stato->log($this->operationId, $fileRimossi . ' file rimossi dal disco.');
+
+            $stato->fase($this->operationId, 'Cancellazione dei dati gestionali', 12);
+
+            DB::transaction(function () use ($stato) {
+                $passi = [
+                    // Le richieste dal modulo pubblico, prima delle assegnazioni che evadono.
+                    'Richieste' => fn () => Richiesta::query()->delete(),
+                    'Assegnazioni' => fn () => Assegnazione::query()->forceDelete(),
+                    'Campagne' => fn () => Campagna::query()->delete(),
+                    // Prima dei territori, e per esteso: le piantine hanno la
+                    // chiave a null on delete, quindi sopravvivevano scollegate
+                    // e con l'immagine che puntava a un file appena cancellato.
+                    'Piantine' => fn () => TerritorioMappa::query()->delete(),
+                    'Storico dei PDF' => fn () => TerritorioPdfVersione::query()->delete(),
+                    'Territori' => fn () => Territorio::query()->withTrashed()->forceDelete(),
+                    'Gruppi di servizio' => fn () => GruppoServizio::query()->delete(),
+                    'Proclamatori' => fn () => Proclamatore::query()->withTrashed()->forceDelete(),
+                    'Tipologie' => fn () => Tipologia::query()->delete(),
+                    'Zone' => fn () => Zona::query()->delete(),
+                    'Anni teocratici' => fn () => AnnoTeocratico::query()->delete(),
+                    'Impostazioni' => fn () => Setting::query()->delete(),
+                ];
+
+                $fatti = 0;
+                foreach ($passi as $etichetta => $azione) {
+                    $azione();
+                    $stato->avanza($this->operationId, ++$fatti);
+                    $stato->log($this->operationId, $etichetta . ': azzerate.');
+                }
+            });
+
+            // Il mass delete non emette eventi, quindi l'istanza memoizzata di
+            // Setting punta ancora alla riga cancellata: senza questo, il
+            // firstOrCreate piu' sotto tornerebbe il fantasma invece di
+            // ricreare la riga.
+            Setting::flushCache();
+
+            // Area della città e anteprime delle pubblicazioni stanno sul disco
+            // privato, che svuotaDiscoPubblico() non tocca: restavano lì e
+            // l'editor ripartiva con la città di prima.
+            Storage::disk('local')->deleteDirectory('piantine');
+            Storage::disk('local')->deleteDirectory('piantine-anteprime');
+            $stato->log($this->operationId, 'Area della città e anteprime delle piantine rimosse.');
+
+            $stato->fase($this->operationId, 'Rimozione degli altri utenti');
+            $utentiRimossi = $this->rimuoviAltriUtenti($stato);
+
+            // Il registro si svuota *dopo* le cancellazioni, non prima: gli
+            // altri utenti sono modelli con LogsActivity, quindi eliminarli
+            // scrive righe nuove che una pulizia anticipata non intercetta e
+            // che resterebbero li' come unica traccia — un residuo, non una
+            // scelta. Svuotato per ultimo, l'unica riga che sopravvive e'
+            // quella scritta apposta qui sotto.
+            $stato->fase($this->operationId, 'Pulizia del registro attivita\'', 1);
+            DB::table('activity_log')->delete();
+            activity()
+                ->causedBy(User::find($this->actorId))
+                ->log('Applicazione azzerata e riportata allo stato iniziale');
+            $stato->avanza($this->operationId, 1);
+
+            $stato->fase($this->operationId, 'Ripristino di ruoli e impostazioni', 3);
+
+            // Ruoli e permessi non vengono cancellati, ma il seeder e' additivo
+            // e idempotente: rieseguirlo garantisce il set di partenza anche se
+            // qualcuno ne aveva rimosso qualcuno a mano.
+            (new RolesAndPermissionsSeeder())->run();
+            $stato->avanza($this->operationId, 1);
+
+            Setting::instance();
+            $stato->avanza($this->operationId, 2);
+
+            $attore = User::find($this->actorId);
+            if ($attore && ! $attore->hasRole('amministratore')) {
+                $attore->assignRole('amministratore');
+            }
+            $stato->avanza($this->operationId, 3);
+        } catch (\Throwable $e) {
+            Log::error('Azzeramento dell\'applicazione non riuscito.', ['exception' => $e]);
+            $stato->markFailed($this->operationId, $e->getMessage());
+
+            return;
+        }
+
+        $messaggio = sprintf(
+            'Applicazione azzerata: dati gestionali rimossi, %d file cancellati, %d utenti eliminati. '
+            . 'Resta il tuo account di amministratore.',
+            $fileRimossi,
+            $utentiRimossi
+        );
+
+        $stato->log($this->operationId, $messaggio);
+        $stato->markCompleted($this->operationId, ['messaggio' => $messaggio]);
+    }
+
+    /**
+     * Vedi CreateBackupArchive::failed(): chiude l'operazione quando il job
+     * muore per cause che handle() non intercetta, liberando il posto unico.
+     */
+    public function failed(?\Throwable $e): void
+    {
+        app(BackupOperationState::class)->markFailed(
+            $this->operationId,
+            ($e?->getMessage() ?: 'Azzeramento interrotto (timeout o errore del worker).')
+            . ' Controlla lo stato dei dati prima di ritentare.'
+        );
+    }
+
+    /**
+     * Cancella ogni utente tranne chi ha chiesto l'azzeramento.
+     *
+     * Uno alla volta e via Eloquent, non con un delete di massa: il trait
+     * HasRoles di Spatie stacca ruoli e permessi nell'evento `deleting`, che un
+     * delete di massa non fa scattare — resterebbero righe orfane in
+     * model_has_roles pronte a essere riassegnate al primo utente che riceve un
+     * id gia' usato.
+     */
+    private function rimuoviAltriUtenti(BackupOperationState $stato): int
+    {
+        $altri = User::query()->where('id', '!=', $this->actorId)->get();
+        $stato->avanza($this->operationId, 0, $altri->count());
+
+        $rimossi = 0;
+        foreach ($altri as $utente) {
+            $utente->delete();
+            $stato->avanza($this->operationId, ++$rimossi);
+        }
+
+        return $rimossi;
+    }
+}

app/Jobs/RestoreBackupArchive.php

@@ -0,0 +1,261 @@
+<?php
+
+namespace App\Jobs;
+
+use App\Livewire\Settings\XmlExchange;
+use App\Models\Setting;
+use App\Services\BackupArchive;
+use App\Services\BackupOperationState;
+use App\Services\Piantine\PiantineBackup;
+use Illuminate\Bus\Queueable;
+use Illuminate\Contracts\Queue\ShouldQueue;
+use Illuminate\Foundation\Bus\Dispatchable;
+use Illuminate\Queue\InteractsWithQueue;
+use Illuminate\Queue\SerializesModels;
+use Illuminate\Support\Facades\Auth;
+use Illuminate\Support\Facades\Cache;
+use Illuminate\Support\Facades\DB;
+use Illuminate\Support\Facades\Log;
+use RuntimeException;
+use Spatie\Permission\PermissionRegistrar;
+
+/**
+ * Ripristina un pacchetto di backup in coda, riportando l'avanzamento fase per
+ * fase (estrazione, database, file).
+ */
+class RestoreBackupArchive implements ShouldQueue
+{
+    use Dispatchable;
+    use InteractsWithQueue;
+    use Queueable;
+    use SerializesModels;
+
+    public int $tries = 1;
+
+    public int $timeout = 570;
+
+    /** Chiave con cui la schermata di cambio password ritrova l'esito. */
+    public const CHIAVE_ESITO = 'restore-esito:';
+
+    public function __construct(
+        public string $operationId,
+        public string $zipPath,
+        public int $actorId,
+    ) {
+    }
+
+    /**
+     * Il ripristino e' tutto o niente. Tre tempi:
+     *
+     *  1. estrazione e verifica dell'archivio nello staging, piantine.json
+     *     compreso: un archivio rotto si ferma qui, a installazione intatta;
+     *  2. un'unica transazione con l'import XML, le tabelle delle piantine, il
+     *     blocco degli account e — per ultimo, ancora dentro — lo scambio dei
+     *     file. Se lo scambio fallisce si disfa da solo e la transazione si
+     *     annulla; se fallisce il commit, i file si rimettono a posto qui;
+     *  3. a commit avvenuto, si buttano i file precedenti.
+     *
+     * Prima import, blocco account e file erano tre passi separati: un errore
+     * sui file lasciava il database gia' riscritto con il disco a meta', e un
+     * errore sul blocco lasciava attive le password del backup.
+     *
+     * Niente TRUNCATE in nessuno dei passi: su MariaDB e' DDL e fa commit
+     * implicito, chiudendo la transazione a meta'. L'import XML e
+     * PiantineBackup cancellano con DELETE.
+     */
+    public function handle(BackupOperationState $stato, BackupArchive $archivio, XmlExchange $exchange, PiantineBackup $piantine): void
+    {
+        $stato->markRunning($this->operationId);
+
+        $staging = null;
+        $scambio = null;
+        $confermato = false;
+
+        try {
+            $stato->fase($this->operationId, 'Estrazione e verifica dell\'archivio');
+
+            $estratto = $archivio->extract(
+                $this->zipPath,
+                fn (int $fatti, int $totale) => $stato->avanza($this->operationId, $fatti, $totale)
+            );
+            $staging = $estratto['staging'];
+
+            $piantine->valida($estratto['piantine']);
+
+            $stato->fase($this->operationId, 'Riscrittura del database', 1);
+
+            // importXmlFromContent() attribuisce a auth()->id() le assegnazioni
+            // il cui autore non e' nel file. Qui non c'e' sessione, quindi
+            // l'utente va reimpostato a mano: senza, l'audit finirebbe sul
+            // primo id disponibile invece che su chi ha avviato il ripristino.
+            //
+            // E' anche cio' che tiene dentro chi ripristina: l'import riconosce
+            // l'attore e ne conserva hash della password, remember_token e
+            // ruolo di amministratore. Con AuthenticateSession attivo, un hash
+            // cambiato chiuderebbe la sua sessione e lo costringerebbe a
+            // rientrare con la password dell'epoca del backup, che puo' non
+            // ricordare. Se il suo account nel backup non c'e', l'import (che
+            // fa upsert per email, senza cancellare nessuno) non lo tocca
+            // affatto: resta con password e ruoli attuali.
+            Auth::onceUsingId($this->actorId);
+
+            DB::transaction(function () use ($stato, $archivio, $exchange, $piantine, $estratto, &$result, &$esitoPiantine, &$utenti, &$scambio) {
+                // La transazione dell'import diventa un savepoint di questa:
+                // il suo commit non e' piu' definitivo.
+                $result = $exchange->importXmlFromContent($estratto['xml']);
+
+                if (isset($result['error'])) {
+                    throw new RuntimeException($result['error']);
+                }
+
+                $esitoPiantine = $piantine->ripristina($estratto['piantine']);
+
+                $utenti = $this->richiediCambioPasswordATutti();
+
+                $stato->avanza($this->operationId, 1, 1);
+                $stato->fase($this->operationId, 'Sostituzione dei file', 1);
+
+                $scambio = $archivio->scambiaFile($estratto);
+            });
+
+            $confermato = true;
+            $archivio->confermaScambio($scambio);
+
+            // L'import ricrea ruoli e assegnazioni, ma Spatie tiene in cache la
+            // mappa permessi-ruoli: senza questo, i processi che l'hanno gia'
+            // caricata continuano a decidere gli accessi con quella di prima
+            // del ripristino, finche' la cache non scade da sola.
+            app(PermissionRegistrar::class)->forgetCachedPermissions();
+
+            $stato->avanza($this->operationId, 1, 1);
+        } catch (\Throwable $e) {
+            $messaggio = $e->getMessage();
+
+            // Lo scambio era riuscito ma il commit no: il database e' tornato
+            // indietro, i file devono seguirlo.
+            if ($scambio !== null && ! $confermato) {
+                try {
+                    $archivio->annullaScambio($scambio, $e);
+                } catch (\Throwable $annullamento) {
+                    $messaggio = $annullamento->getMessage();
+                }
+            }
+
+            // La transazione annullata non svuota le cache in memoria del
+            // processo: Setting terrebbe l'istanza creata dall'import (una
+            // riga che non esiste piu') e Spatie i ruoli letti durante l'import.
+            Setting::flushCache();
+            app(PermissionRegistrar::class)->forgetCachedPermissions();
+
+            Log::error('Ripristino del backup non riuscito.', ['exception' => $e]);
+            $stato->markFailed($this->operationId, $messaggio);
+
+            return;
+        } finally {
+            Auth::forgetUser();
+
+            if ($staging !== null) {
+                $archivio->deleteDirectory($staging);
+            }
+
+            @unlink($this->zipPath);
+        }
+
+        $stats = $result['stats'];
+        $stats['piantine_ripristinate'] = $esitoPiantine['mappe'];
+        $stats['versioni_pdf_ripristinate'] = $esitoPiantine['versioni'];
+        $fileRipristinati = $scambio['file'];
+
+        $messaggio = sprintf(
+            'Ripristino completato: %d territori, %d proclamatori, %d assegnazioni, %d piantine e %d file ripristinati. '
+            . 'Per sicurezza %s impostare una nuova password.',
+            $stats['territori_importati'] ?? 0,
+            $stats['proclamatori_importati'] ?? 0,
+            $stats['assegnazioni_importate'] ?? 0,
+            $esitoPiantine['mappe'],
+            $fileRipristinati,
+            $utenti === 1 ? 'l\'unico account deve' : 'tutti i ' . $utenti . ' account devono'
+        );
+
+        // Un archivio di formato 1 non conteneva le piantine: va detto, o
+        // l'amministratore le cercherebbe senza sapere perche' sono sparite.
+        if ($estratto['piantine'] === null) {
+            $stato->log(
+                $this->operationId,
+                'Archivio di un formato precedente: non contiene piantine e storico dei PDF, che restano vuoti. '
+                . 'L\'area KML in uso non e\' stata toccata.'
+            );
+        }
+
+        // Il messaggio non puo' viaggiare in sessione (qui non ce n'e' una) e la
+        // pagina che dovra' mostrarlo non e' questa: appena il flag e' acceso,
+        // il middleware dirotta l'amministratore sul cambio password. Lo si
+        // lascia in cache a suo nome, e quella schermata lo consuma.
+        Cache::put(self::CHIAVE_ESITO . $this->actorId, $messaggio, 3600);
+
+        $stato->log($this->operationId, $messaggio);
+        $stato->markCompleted($this->operationId, [
+            'stats' => $stats,
+            'issues' => array_slice(array_merge($result['issues'], $esitoPiantine['issues']), 0, 50),
+            'file_ripristinati' => $fileRipristinati,
+            'messaggio' => $messaggio,
+        ]);
+    }
+
+    /**
+     * Vedi CreateBackupArchive::failed(): chiude l'operazione quando il job
+     * muore per cause che handle() non intercetta, cosi' il posto unico si
+     * libera subito invece di restare occupato fino alla scadenza.
+     *
+     * Qui il messaggio dice anche in che stato si e' rimasti. Un processo
+     * ucciso a meta' non arriva al commit, e il database annulla da se' la
+     * transazione rimasta aperta: i dati restano quelli di prima. L'unica
+     * finestra scoperta e' quella, di pochi millisecondi, fra lo scambio dei
+     * file e il commit — in quel caso i file precedenti sono ancora in
+     * storage/app/backup-precedenti/. La strada resta rilanciare il
+     * ripristino, non ignorare l'errore.
+     */
+    public function failed(?\Throwable $e): void
+    {
+        app(BackupOperationState::class)->markFailed(
+            $this->operationId,
+            ($e?->getMessage() ?: 'Ripristino interrotto (timeout o errore del worker).')
+            . ' Un ripristino interrotto prima della conferma non modifica il database: rilancialo con lo stesso pacchetto. '
+            . 'Se i file risultano diversi, quelli precedenti sono in storage/app/backup-precedenti/.'
+        );
+
+        @unlink($this->zipPath);
+    }
+
+    /**
+     * Blocca ogni account finche' non sceglie una password nuova,
+     * l'amministratore che sta ripristinando compreso.
+     *
+     * Il pacchetto contiene gli hash bcrypt di tutti gli utenti: chi ha avuto
+     * il file fra le mani ha potuto tentarne il crack con calma, quindi dopo un
+     * ripristino nessuna delle vecchie password si puo' considerare segreta.
+     * Anche i remember_token vengono azzerati: sono credenziali persistenti a
+     * tutti gli effetti e stanno pure loro nel backup.
+     *
+     * Scritto con il query builder di proposito — un update di massa su
+     * Eloquent qui non aggiungerebbe nulla e toccherebbe updated_at su tutte le
+     * righe appena importate con i loro timestamp originali.
+     *
+     * @return int Account bloccati. Non e' il valore di ritorno dell'update:
+     *             MariaDB conta le righe *cambiate*, quindi un utente gia'
+     *             marcato da un ripristino precedente non comparirebbe e il
+     *             riepilogo direbbe meno account di quanti ne sono bloccati.
+     */
+    private function richiediCambioPasswordATutti(): int
+    {
+        DB::table('users')->update([
+            'password_change_required' => true,
+            // Il motivo ora è il ripristino, anche per chi aveva una
+            // password temporanea (pagina del cambio password).
+            'password_temporanea' => false,
+            'remember_token' => null,
+        ]);
+
+        return (int) DB::table('users')->count();
+    }
+}

app/Livewire/Assegnazioni/Assegna.php

@@ -2,29 +2,70 @@
 
 namespace App\Livewire\Assegnazioni;
 
+use App\Livewire\Concerns\InviaLink;
+use App\Livewire\Concerns\RicordaRitorno;
 use Livewire\Component;
-use Livewire\Attributes\Computed;
 use App\Models\Territorio;
 use App\Models\Proclamatore;
 use App\Models\Assegnazione;
 use App\Models\AnnoTeocratico;
-use Illuminate\Support\Facades\Storage;
+use App\Models\Richiesta;
+use Illuminate\Support\Facades\DB;
+use Livewire\Attributes\Locked;
 
 class Assegna extends Component
 {
+    use RicordaRitorno;
+    use InviaLink;
+
     public ?int $territorio_id = null;
     public ?int $proclamatore_id = null;
     public string $assigned_at = '';
-    public string $territorioSearch = '';
+
+    /** Il proclamatore ha chiesto la cartolina cartacea (elenco Cartacei). */
+    public bool $cartaceo = false;
+
+    /**
+     * La richiesta dal modulo pubblico da cui si è partiti (?richiesta=,
+     * dalla Home): si mostra sopra il modulo e, fatta l'assegnazione, risulta
+     * evasa. Locked: la imposta solo mount().
+     */
+    #[Locked]
+    public ?int $richiestaId = null;
 
     // Optional pre-selection from parent context
     public ?int $preselectedTerritorioId = null;
 
+    /**
+     * Aperta da "Assegna →" della Home (?dalla_home=1, lo mette solo la Home)
+     * la pagina serve ad assegnare quel territorio: l'elenco dei territori
+     * assegnati sotto il modulo non si mostra (né si carica).
+     */
+    public bool $elencoNascosto = false;
+
     public function mount(?int $territorioId = null)
     {
         $this->preselectedTerritorioId = $territorioId;
         $this->territorio_id = $territorioId;
         $this->assigned_at = now()->format('Y-m-d');
+        $this->elencoNascosto = request()->boolean('dalla_home');
+
+        // Dalla Home, da una richiesta: il proclamatore scelto fra i nomi
+        // simili arriva già impostato (?proclamatore=), il resto del modulo è
+        // quello di sempre.
+        if (($id = request()->integer('proclamatore')) && Proclamatore::attivi()->whereKey($id)->exists()) {
+            $this->proclamatore_id = $id;
+        }
+        if (($id = request()->integer('richiesta')) && auth()->user()->can('richieste.gestisci')
+            && Richiesta::aperte()->whereKey($id)->exists()) {
+            $this->richiestaId = $id;
+        }
+
+        // ?invia=<id>: riprende l'invio di un link rimasto in sospeso (dalla
+        // scheda del territorio).
+        if ($invia = request()->integer('invia')) {
+            $this->apriInvio($invia);
+        }
     }
 
     protected function rules(): array
@@ -42,100 +83,133 @@ class Assegna extends Component
 
         $territorio = Territorio::findOrFail($this->territorio_id);
 
-        // Check territory is available (not currently assigned)
+        // Gli errori vanno sul campo e non in sessione: il messaggio flash
+        // sta nel telaio della pagina, che Livewire non ridisegna, e il
+        // rifiuto passerebbe inosservato.
         if ($territorio->assegnazioneCorrente) {
-            session()->flash('error', "Il territorio {$territorio->numero} è già assegnato a {$territorio->assegnazioneCorrente->proclamatore->nome_completo}.");
+            $this->addError('territorio_id', "Il territorio {$territorio->numero} è già assegnato a {$territorio->assegnazioneCorrente->proclamatore->nome_completo}.");
             return;
         }
 
-        // Check territory is active
         if (!$territorio->attivo) {
-            session()->flash('error', "Il territorio {$territorio->numero} è inattivo.");
+            $this->addError('territorio_id', "Il territorio {$territorio->numero} è inattivo.");
+            return;
+        }
+
+        // Nel pacchetto di un gruppo di servizio: lo assegna il sorvegliante.
+        if ($territorio->gruppo_servizio_id) {
+            $this->addError('territorio_id', "Il territorio {$territorio->numero} è nel pacchetto del gruppo {$territorio->gruppo?->nome}: lo assegna il sorvegliante, oppure va prima tolto dal pacchetto.");
             return;
         }
 
         $proclamatore = Proclamatore::findOrFail($this->proclamatore_id);
         if (!$proclamatore->attivo) {
-            session()->flash('error', "Il proclamatore {$proclamatore->nome_completo} è inattivo.");
+            $this->addError('proclamatore_id', "Il proclamatore {$proclamatore->nome_completo} è inattivo.");
             return;
         }
 
         $assignedDate = \Carbon\Carbon::parse($this->assigned_at);
         $annoTeocratico = AnnoTeocratico::perData($assignedDate);
 
-        $assegnazione = Assegnazione::create([
-            'territorio_id' => $this->territorio_id,
-            'proclamatore_id' => $this->proclamatore_id,
-            'anno_teocratico_id' => $annoTeocratico->id,
-            'assigned_at' => $assignedDate,
-            'created_by' => auth()->id(),
-        ]);
+        // Controllo e inserimento sotto lo stesso lock sulla riga del
+        // territorio: un doppio clic o due schede aperte non possono più
+        // superare entrambi il controllo e creare due assegnazioni aperte.
+        $esito = DB::transaction(function () use ($territorio, $assignedDate, $annoTeocratico) {
+            Territorio::whereKey($territorio->id)->lockForUpdate()->first();
+
+            $conflitto = Assegnazione::sovrappostaA($territorio->id, $assignedDate);
+            if ($conflitto) {
+                return "Il territorio {$territorio->numero} risulta assegnato {$conflitto->descrizionePeriodo()}: "
+                    . ($conflitto->returned_at
+                        ? 'la data di assegnazione non può essere precedente al suo rientro.'
+                        : 'registrane prima il rientro.');
+            }
+
+            return Assegnazione::create([
+                'territorio_id' => $this->territorio_id,
+                'proclamatore_id' => $this->proclamatore_id,
+                'anno_teocratico_id' => $annoTeocratico->id,
+                'assigned_at' => $assignedDate,
+                'created_by' => auth()->id(),
+                // C'è un link da mandare solo se il territorio ha il PDF.
+                'link_da_inviare' => (bool) $territorio->pdf_path,
+                'cartaceo' => $this->cartaceo,
+            ]);
+        });
+
+        if (is_string($esito)) {
+            $this->addError('assigned_at', $esito);
+
+            return;
+        }
+
+        $assegnazione = $esito;
 
         activity()->causedBy(auth()->user())
             ->performedOn($assegnazione)
+            // L'id, non il nome: nome e cognome sono cifrati nel database, e
+            // copiati qui in chiaro restavano leggibili anche dopo
+            // l'anonimizzazione. Il registro mostra il nome di oggi.
             ->withProperties([
                 'territorio' => $territorio->numero,
-                'proclamatore' => $proclamatore->nome_completo,
+                'proclamatore_id' => $proclamatore->id,
             ])
             ->log('assigned');
 
-        session()->flash('success', "Territorio {$territorio->numero} assegnato a {$proclamatore->nome_completo}.");
-        return $this->redirect(route('territori.show', $territorio), navigate: true);
-    }
-
-    public function toggleLinkSent(int $assegnazioneId): void
-    {
-        $this->authorize('territori.assign');
-        $assegnazione = Assegnazione::findOrFail($assegnazioneId);
-        $assegnazione->forceFill(['link_sent' => ! $assegnazione->link_sent])->saveQuietly();
-    }
-
-    #[Computed]
-    public function selectedThumbnailUrl(): ?string
-    {
-        if (!$this->territorio_id) {
-            return null;
+        // Partita da una richiesta del modulo pubblico: ora è evasa.
+        if ($this->richiestaId) {
+            Richiesta::find($this->richiestaId)?->evadi($assegnazione, auth()->user());
+            $this->richiestaId = null;
         }
-        $t = Territorio::find($this->territorio_id);
-        return $t?->thumbnail_path ? Storage::url($t->thumbnail_path) : null;
+        $this->cartaceo = false;
+
+        // Non si va avanti: si apre l'invio del link (vedi in cima).
+        $this->apriInvio($assegnazione->id);
+    }
+
+    // ─── Invio del link (trait InviaLink) ──────────────────────
+
+    protected function puoInviare(Assegnazione $assegnazione): bool
+    {
+        return auth()->user()->can('territori.assign');
+    }
+
+    protected function paginaDopoInvio(): string
+    {
+        return $this->destinazione(route('assegnazioni.assegna'));
     }
 
     public function render()
     {
-        $territoriQuery = Territorio::where('attivo', true)
-            ->whereDoesntHave('assegnazioni', fn($q) => $q->aperte())
-            ->with(['zona', 'tipologia']);
-
-        if (trim($this->territorioSearch) !== '') {
-            $term = trim($this->territorioSearch);
-            $territoriQuery->where(function ($q) use ($term) {
-                $q->where('numero', 'like', "%{$term}%")
-                    ->orWhereHas('zona', fn($z) => $z->where('nome', 'like', "%{$term}%"))
-                    ->orWhereHas('tipologia', fn($t) => $t->where('nome', 'like', "%{$term}%"));
-            });
-        }
-
-        $territoriDisponibili = $territoriQuery
-            ->orderBy('numero')
-            ->get();
-
-        $proclamatoriAttivi = Proclamatore::attivi()
+        // Le opzioni dei campi di scelta con ricerca (<x-scelta>). Ci sono anche
+        // i territori già assegnati, che non si possono scegliere: cercandone
+        // uno si legge a chi è, invece di un "nessun risultato". La miniatura
+        // serve all'anteprima, che si aggiorna nel browser.
+        // Quelli nel pacchetto di un gruppo di servizio li assegna il
+        // sorvegliante: qui si trovano ma non si scelgono.
+        $territori = Territorio::attivi()
+            ->with(['zona', 'tipologia', 'assegnazioneCorrente.proclamatore', 'gruppo'])
             ->get()
-            ->sortBy(fn($p) => mb_strtolower($p->cognome . ' ' . $p->nome));
+            ->sortBy('numero', SORT_NATURAL);
 
-        // All currently assigned territories with links
-        $assegnazioniAperte = Assegnazione::aperte()
-            ->with(['territorio.zona', 'proclamatore'])
-            ->get()
-            ->sortBy(fn($a) => (int) $a->territorio?->numero);
+        $opzioniTerritori = $territori
+            ->map(fn (Territorio $t) => $t->opzioneScelta(match (true) {
+                (bool) $t->assegnazioneCorrente => 'già assegnato a ' . ($t->assegnazioneCorrente->proclamatore?->nome_completo ?? '—'),
+                (bool) $t->gruppo_servizio_id => 'nel pacchetto del gruppo ' . ($t->gruppo?->nome ?? ''),
+                default => null,
+            }) + array_filter(['miniatura' => $t->miniaturaUrl()]))
+            ->values()
+            ->all();
 
-        $linkTtlMonths = max(1, (int) \App\Models\Setting::getValue('assignment_link_ttl_hours', 1));
+        $opzioniProclamatori = Proclamatore::opzioniScelta(Proclamatore::attivi()->get());
 
+        // L'elenco dei territori assegnati sta in ElencoAssegnati.
         return view('livewire.assegnazioni.assegna', [
-            'territoriDisponibili' => $territoriDisponibili,
-            'proclamatoriAttivi' => $proclamatoriAttivi,
-            'assegnazioniAperte' => $assegnazioniAperte,
-            'linkTtlMonths' => $linkTtlMonths,
+            'invio' => $this->invioCorrente(),
+            'opzioniTerritori' => $opzioniTerritori,
+            'opzioniProclamatori' => $opzioniProclamatori,
+            'anteprimaIniziale' => $this->territorio_id ? $territori->firstWhere('id', $this->territorio_id)?->miniaturaUrl() : null,
+            'richiesta' => $this->richiestaId ? Richiesta::find($this->richiestaId) : null,
         ]);
     }
 }

app/Livewire/Assegnazioni/Cartacei.php

@@ -0,0 +1,25 @@
+<?php
+
+namespace App\Livewire\Assegnazioni;
+
+use App\Models\Assegnazione;
+use Livewire\Component;
+
+/**
+ * I territori fuori in cartaceo, e a chi: le assegnazioni aperte per cui il
+ * proclamatore ha chiesto la cartolina (spunta "cartaceo" su Assegna o in "Il
+ * mio gruppo"). Al rientro escono dall'elenco.
+ */
+class Cartacei extends Component
+{
+    public function render()
+    {
+        return view('livewire.assegnazioni.cartacei', [
+            'assegnazioni' => Assegnazione::aperte()
+                ->where('cartaceo', true)
+                ->with(['territorio.zona', 'proclamatore'])
+                ->orderBy('assigned_at')
+                ->get(),
+        ]);
+    }
+}

app/Livewire/Assegnazioni/ElencoAssegnati.php

@@ -0,0 +1,67 @@
+<?php
+
+namespace App\Livewire\Assegnazioni;
+
+use App\Models\Assegnazione;
+use App\Models\Setting;
+use Illuminate\Support\Str;
+use Livewire\Attributes\Lazy;
+use Livewire\Component;
+
+/**
+ * L'elenco dei territori assegnati della pagina Assegna, separato dal form.
+ *
+ * Prima stava nello stesso componente: con ~80 righe la pagina pesava quasi
+ * 400 KB e Livewire li rimandava tutti a ogni interazione (scegliere un
+ * territorio, scrivere nella ricerca, aprire l'invio del link). Ora:
+ * - è un componente a sé, caricato subito dopo la pagina (#[Lazy]): il form
+ *   compare subito e le sue azioni non ridisegnano l'elenco;
+ * - la ricerca filtra le righe nel browser (data-cerca), senza richieste;
+ * - le icone sono simboli SVG definiti una volta e richiamati con <use>.
+ */
+#[Lazy]
+class ElencoAssegnati extends Component
+{
+    public function toggleLinkSent(int $assegnazioneId): void
+    {
+        $this->authorize('territori.assign');
+        $assegnazione = Assegnazione::findOrFail($assegnazioneId);
+        $assegnazione->registraInvioLink(! $assegnazione->link_sent, $assegnazione->link_canale);
+    }
+
+    /** "Condividi" dall'elenco andato a buon fine: il link risulta inviato. */
+    public function segnaCondiviso(int $assegnazioneId): void
+    {
+        $this->authorize('territori.assign');
+        Assegnazione::aperte()->find($assegnazioneId)?->registraInvioLink(true, 'condividi');
+    }
+
+    public function placeholder()
+    {
+        return view('livewire.assegnazioni.elenco-assegnati-attesa');
+    }
+
+    public function render()
+    {
+        $assegnazioni = Assegnazione::aperte()
+            ->with(['territorio.zona', 'proclamatore'])
+            ->get()
+            ->sortBy(fn ($a) => (string) $a->territorio?->numero, SORT_NATURAL)
+            ->values();
+
+        // Il testo su cui filtra la ricerca nel browser: numero, zona e nome
+        // (decifrato qui: in SQL non si potrebbe cercare), senza accenti.
+        $cerca = $assegnazioni->mapWithKeys(fn ($a) => [$a->id => Str::lower(Str::ascii(implode(' ', array_filter([
+            $a->territorio?->numero,
+            $a->territorio?->zona?->nome,
+            $a->proclamatore?->nome_completo,
+        ]))))]);
+
+        return view('livewire.assegnazioni.elenco-assegnati', [
+            'assegnazioni' => $assegnazioni,
+            'cerca' => $cerca,
+            // Il link scade alla soglia rientro (giorni_per_smarrito).
+            'sogliaRientro' => max(1, (int) Setting::getValue('giorni_per_smarrito', 120)),
+        ]);
+    }
+}

app/Livewire/Assegnazioni/Rientra.php

@@ -3,12 +3,16 @@
 namespace App\Livewire\Assegnazioni;
 
 use Livewire\Attributes\Locked;
+use App\Livewire\Concerns\RicordaRitorno;
 use Livewire\Component;
 use App\Models\Assegnazione;
 use App\Models\Campagna;
+use App\Models\Richiesta;
 
 class Rientra extends Component
 {
+    use RicordaRitorno;
+
     public Assegnazione $assegnazione;
     public string $returned_at = '';
     public bool $showCampaignPrompt = false;
@@ -22,14 +26,27 @@ class Rientra extends Component
 
     public bool $counted_in_campaign = false;
 
+    /**
+     * La richiesta di riconsegna dal modulo pubblico da cui si è partiti
+     * (?richiesta=, dalla Home): registrato il rientro, risulta evasa.
+     */
+    #[Locked]
+    public ?int $richiestaId = null;
+
     public function mount(Assegnazione $assegnazione)
     {
+        $this->autorizza($assegnazione);
         $this->assegnazione = $assegnazione->load(['territorio', 'proclamatore']);
 
         if ($assegnazione->returned_at) {
             abort(404, 'Assegnazione già rientrata.');
         }
 
+        if (($id = request()->integer('richiesta')) && auth()->user()->can('richieste.gestisci')
+            && Richiesta::aperte()->whereKey($id)->exists()) {
+            $this->richiestaId = $id;
+        }
+
         $this->returned_at = now()->format('Y-m-d');
         $this->checkCampaign();
     }
@@ -66,8 +83,28 @@ class Rientra extends Component
         ];
     }
 
+    /**
+     * Chi ha territori.return registra qualsiasi rientro. Il sorvegliante di
+     * gruppo (gruppo.gestisci) solo quelli del suo gruppo: assegnazioni nate
+     * dal gruppo o territori del suo pacchetto.
+     */
+    private function autorizza(Assegnazione $assegnazione): void
+    {
+        $utente = auth()->user();
+        if ($utente->can('territori.return')) {
+            return;
+        }
+
+        $gruppo = $utente->can('gruppo.gestisci') ? $utente->gruppoSorvegliato() : null;
+        abort_unless(
+            $gruppo && ($assegnazione->gruppo_servizio_id === $gruppo->id || $assegnazione->territorio?->gruppo_servizio_id === $gruppo->id),
+            403
+        );
+    }
+
     public function save()
     {
+        $this->autorizza($this->assegnazione);
         $this->validate();
 
         // mount() rejects an already-returned assignment, but the component
@@ -92,22 +129,60 @@ class Rientra extends Component
             ->performedOn($this->assegnazione)
             ->withProperties([
                 'territorio' => $territorio->numero,
-                'proclamatore' => $proclamatore->nome_completo,
+                'proclamatore_id' => $proclamatore->id, // vedi Assegna: niente nomi in chiaro
                 'giorni' => $this->assegnazione->giorni,
                 'campagna' => $this->counted_in_campaign,
             ])
             ->log('returned');
 
+        // The operator answered the campaign prompt: record the choice
+        // (counted or not) as its own audit entry.
+        if ($this->showCampaignPrompt && $this->campagna_id) {
+            $this->assegnazione->logCampagnaPercorso(
+                Campagna::find($this->campagna_id),
+                $this->counted_in_campaign,
+                'Rientro'
+            );
+        }
+
+        // Partito da una richiesta di riconsegna (Home): ora è evasa.
+        if ($this->richiestaId) {
+            Richiesta::find($this->richiestaId)?->evadi($this->assegnazione, auth()->user());
+        }
+
         session()->flash('success', "Territorio {$territorio->numero} rientrato da {$proclamatore->nome_completo} dopo {$this->assegnazione->giorni} giorni.");
-        return $this->redirect(route('territori.show', $territorio), navigate: true);
+        return $this->redirect($this->destinazione($this->paginaPredefinita()), navigate: true);
+    }
+
+    /**
+     * Dove si torna senza una pagina di partenza: la scheda del territorio,
+     * o "Il mio gruppo" per il sorvegliante, che la scheda non la vede.
+     */
+    public function paginaPredefinita(): string
+    {
+        return auth()->user()->can('territori.assign')
+            ? route('territori.show', $this->assegnazione->territorio_id)
+            : route('mio-gruppo');
     }
 
     public function render()
     {
         $campagna = $this->campagna_id ? Campagna::find($this->campagna_id) : null;
 
+        // Warning shown inside the campaign prompt only: holding time up to
+        // the selected return date above the "da rientrare" threshold.
+        $giorniPercorrenza = null;
+        $sogliaPercorrenza = null;
+        if ($campagna && $this->returned_at) {
+            $giorniPercorrenza = $this->assegnazione->giorniPercorrenza(\Carbon\Carbon::parse($this->returned_at));
+            $sogliaPercorrenza = Assegnazione::sogliaPercorrenzaElevata();
+        }
+
         return view('livewire.assegnazioni.rientra', [
             'campagna' => $campagna,
+            'giorniPercorrenza' => $giorniPercorrenza,
+            'sogliaPercorrenza' => $sogliaPercorrenza,
+            'richiesta' => $this->richiestaId ? Richiesta::find($this->richiestaId) : null,
         ]);
     }
 }

app/Livewire/AuditLog.php

@@ -48,8 +48,22 @@ class AuditLog extends Component
         $events = Activity::select('description')->distinct()->pluck('description');
         $users = \App\Models\User::orderBy('name')->get();
 
+        $activities = $query->paginate(30);
+
+        // Il log conserva solo l'id del proclamatore: il nome si legge adesso,
+        // così chi è stato anonimizzato compare come tale anche nello storico.
+        $idProclamatori = $activities->getCollection()
+            ->map(fn ($a) => data_get($a->properties, 'proclamatore_id'))
+            ->filter()
+            ->unique();
+        $nomiProclamatori = \App\Models\Proclamatore::withTrashed()
+            ->whereIn('id', $idProclamatori)
+            ->get()
+            ->mapWithKeys(fn ($p) => [$p->id => $p->nome_completo]);
+
         return view('livewire.audit-log', [
-            'activities' => $query->paginate(30),
+            'activities' => $activities,
+            'nomiProclamatori' => $nomiProclamatori,
             'events' => $events,
             'users' => $users,
         ]);

app/Livewire/Campagne/CampagnaCreate.php

@@ -2,11 +2,14 @@
 
 namespace App\Livewire\Campagne;
 
+use App\Livewire\Concerns\RicordaRitorno;
 use Livewire\Component;
 use App\Models\Campagna;
 
 class CampagnaCreate extends Component
 {
+    use RicordaRitorno;
+
     public string $descrizione = '';
     public string $start_date = '';
     public string $end_date = '';
@@ -22,6 +25,9 @@ class CampagnaCreate extends Component
 
     public function save()
     {
+        // Creazione campagne riservata all'amministratore.
+        $this->authorize('settings.manage');
+
         $this->validate();
 
         $campagna = Campagna::create([
@@ -31,7 +37,7 @@ class CampagnaCreate extends Component
         ]);
 
         session()->flash('success', "Campagna '{$campagna->descrizione}' creata.");
-        return $this->redirect(route('campagne.index'), navigate: true);
+        return $this->redirect($this->destinazione(route('campagne.index')), navigate: true);
     }
 
     public function render()

app/Livewire/Campagne/CampagnaEdit.php

@@ -2,11 +2,14 @@
 
 namespace App\Livewire\Campagne;
 
+use App\Livewire\Concerns\RicordaRitorno;
 use Livewire\Component;
 use App\Models\Campagna;
 
 class CampagnaEdit extends Component
 {
+    use RicordaRitorno;
+
     public Campagna $campagna;
     public string $descrizione = '';
     public string $start_date = '';
@@ -14,6 +17,9 @@ class CampagnaEdit extends Component
 
     public function mount(Campagna $campagna)
     {
+        // Modifica campagne riservata all'amministratore.
+        $this->authorize('settings.manage');
+
         $this->campagna = $campagna;
         $this->descrizione = $campagna->descrizione;
         $this->start_date = $campagna->start_date->format('Y-m-d');
@@ -31,6 +37,10 @@ class CampagnaEdit extends Component
 
     public function save()
     {
+        // Re-check on the update request: route middleware guards the initial
+        // load, but the action can be replayed on a persisted component.
+        $this->authorize('settings.manage');
+
         $this->validate();
 
         $this->campagna->update([
@@ -40,7 +50,7 @@ class CampagnaEdit extends Component
         ]);
 
         session()->flash('success', "Campagna aggiornata.");
-        return $this->redirect(route('campagne.index'), navigate: true);
+        return $this->redirect($this->destinazione(route('campagne.index')), navigate: true);
     }
 
     public function render()

app/Livewire/Campagne/CampagnaIndex.php

@@ -2,19 +2,26 @@
 
 namespace App\Livewire\Campagne;
 
+use App\Livewire\Concerns\Avvisa;
 use Livewire\Component;
 use Livewire\WithPagination;
 use App\Models\Campagna;
 
 class CampagnaIndex extends Component
 {
+    use Avvisa;
     use WithPagination;
 
     public function deleteCampagna(int $id)
     {
+        // Eliminazione campagne riservata all'amministratore. La index è
+        // accessibile a chiunque abbia campagne.manage, quindi il gate deve
+        // stare qui, non solo sul middleware di route.
+        $this->authorize('settings.manage');
+
         $campagna = Campagna::findOrFail($id);
         $campagna->delete();
-        session()->flash('success', "Campagna '{$campagna->descrizione}' eliminata.");
+        $this->avvisa("Campagna '{$campagna->descrizione}' eliminata.");
     }
 
     public function render()

app/Livewire/Campagne/CampagnaShow.php

@@ -2,6 +2,7 @@
 
 namespace App\Livewire\Campagne;
 
+use App\Livewire\Concerns\RicordaRitorno;
 use Livewire\Component;
 use App\Models\Campagna;
 use App\Models\Assegnazione;
@@ -9,6 +10,8 @@ use App\Models\Territorio;
 
 class CampagnaShow extends Component
 {
+    use RicordaRitorno;
+
     public Campagna $campagna;
 
     public function mount(Campagna $campagna)
@@ -18,16 +21,28 @@ class CampagnaShow extends Component
 
     public function render()
     {
-        // Assignments counted for this campaign:
-        // - assigned on or after campaign start
-        // - linked to this campaign (campaign_id), regardless of returned_at (retroactive returns allowed)
-        $conteggiate = Assegnazione::where('campaign_id', $this->campagna->id)
-            ->where('counted_in_campaign', true)
-            ->where('assigned_at', '>=', $this->campagna->start_date)
+        // Le assegnazioni contate per la campagna, cioè quelle per cui al
+        // rientro si è risposto sì (campagnaApplicabile propone anche quelle
+        // uscite poco prima dell'inizio e rientrate durante). Le stesse della
+        // percentuale: prima qui si scartavano quelle uscite prima dell'inizio,
+        // e l'elenco era più corto di quanto la percentuale contasse.
+        $conteggiate = $this->campagna->assegnazioniConteggiate()
             ->with(['territorio', 'proclamatore'])
             ->orderBy('returned_at')
             ->get();
 
+        // Open assignments can still be counted for this campaign only while
+        // no later campaign has started: on return the most recent one is
+        // offered (see Assegnazione::campagnaApplicabile()).
+        $superata = Campagna::where('start_date', '>', $this->campagna->start_date)
+            ->where('start_date', '<=', now()->toDateString())
+            ->exists();
+
+        $inCorso = $superata ? null : $this->campagna->assegnazioniInCorso()
+            ->with(['territorio', 'proclamatore'])
+            ->orderBy('assigned_at')
+            ->get();
+
         // All assignments that were active during this campaign range
         $assegnateNelRange = Assegnazione::where('assigned_at', '<=', $this->campagna->end_date)
             ->where(function ($q) {
@@ -38,6 +53,7 @@ class CampagnaShow extends Component
 
         return view('livewire.campagne.campagna-show', [
             'conteggiate' => $conteggiate,
+            'inCorso' => $inCorso,
             'assegnateNelRange' => $assegnateNelRange,
         ]);
     }

app/Livewire/Concerns/Avvisa.php

@@ -0,0 +1,25 @@
+<?php
+
+namespace App\Livewire\Concerns;
+
+/**
+ * Avvisi a comparsa che funzionano dopo un'azione Livewire.
+ *
+ * session()->flash() non basta: il messaggio sta nel telaio della pagina, e
+ * dopo un'azione Livewire ridisegna solo il componente. L'avviso compariva
+ * solo al caricamento completo successivo, fuori contesto, e un salvataggio
+ * rifiutato sembrava riuscito. Qui l'avviso parte come evento del browser e
+ * lo raccoglie <x-avvisi> nel telaio, che resta sempre in pagina.
+ */
+trait Avvisa
+{
+    protected function avvisa(string $testo, string $tipo = 'ok'): void
+    {
+        $this->dispatch('avviso', tipo: $tipo === 'errore' ? 'errore' : 'ok', testo: $testo);
+    }
+
+    protected function avvisaErrore(string $testo): void
+    {
+        $this->avvisa($testo, 'errore');
+    }
+}

app/Livewire/Concerns/InviaLink.php

@@ -0,0 +1,132 @@
+<?php
+
+namespace App\Livewire\Concerns;
+
+use App\Models\Assegnazione;
+use Livewire\Attributes\Locked;
+use Livewire\Attributes\On;
+
+/**
+ * Invio del link della piantina dopo un'assegnazione, condiviso dalla pagina
+ * Assegna e da "Il mio gruppo" del sorvegliante. La vista è il partial
+ * livewire/assegnazioni/_invio-link.
+ *
+ * Dopo l'assegnazione non si va avanti: si sceglie il canale (copia link o
+ * Condividi: il destinatario lo sceglie chi usa l'app dai suoi contatti, i
+ * proclamatori non hanno numero né email), si dice se il link è partito, e
+ * solo allora si va avanti. Se la procedura si interrompe, l'assegnazione
+ * resta con link_da_inviare e lo si segnala dove compare.
+ *
+ * Chi usa il trait dice chi può mandare il link di un'assegnazione
+ * (puoInviare) e dove si va dopo (paginaDopoInvio).
+ */
+trait InviaLink
+{
+    /** L'assegnazione di cui si sta mandando il link. */
+    #[Locked]
+    public ?int $invioId = null;
+
+    /** Il canale usato in questo invio (Assegnazione::CANALI_LINK). */
+    #[Locked]
+    public ?string $canaleUsato = null;
+
+    public string $erroreInvio = '';
+
+    abstract protected function puoInviare(Assegnazione $assegnazione): bool;
+
+    abstract protected function paginaDopoInvio(): string;
+
+    /**
+     * Apre l'invio: subito dopo l'assegnazione, o da un'assegnazione rimasta
+     * in sospeso ("Invia link" nell'elenco, che lo chiede con apri-invio).
+     */
+    #[On('apri-invio')]
+    public function apriInvio(int $assegnazioneId): void
+    {
+        $assegnazione = Assegnazione::aperte()->find($assegnazioneId);
+        if (! $assegnazione) {
+            return;
+        }
+        abort_unless($this->puoInviare($assegnazione), 403);
+
+        $this->invioId = $assegnazione->id;
+        $this->canaleUsato = null;
+        $this->erroreInvio = '';
+    }
+
+    /** Copia link o Condividi: l'invio vero lo fa chi usa l'app, qui si annota il canale. */
+    public function canale(string $canale): void
+    {
+        $assegnazione = $this->assegnazioneInInvio();
+        if (! $assegnazione || ! in_array($canale, Assegnazione::CANALI_ATTIVI, true) || ! $assegnazione->shortPdfUrl()) {
+            return;
+        }
+
+        $this->canaleUsato = $canale;
+        $this->erroreInvio = '';
+    }
+
+    /**
+     * La risposta a "Hai inviato il link?": la si registra e solo adesso si
+     * va avanti. "Sì" vuole un canale usato; "No" lascia il link da inviare.
+     */
+    public function concludiInvio(bool $inviato)
+    {
+        $assegnazione = $this->assegnazioneInInvio();
+        if (! $assegnazione) {
+            $this->invioId = null;
+
+            return null;
+        }
+
+        if ($inviato && $this->canaleUsato === null) {
+            $this->erroreInvio = 'Scegli prima come mandare il link.';
+
+            return null;
+        }
+
+        $assegnazione->registraInvioLink($inviato, $this->canaleUsato);
+
+        // Nel log il canale e l'id del proclamatore, mai il nome.
+        activity()->causedBy(auth()->user())
+            ->performedOn($assegnazione)
+            ->withProperties([
+                'territorio' => $assegnazione->territorio?->numero,
+                'proclamatore_id' => $assegnazione->proclamatore_id,
+                'canale' => $inviato ? $this->canaleUsato : null,
+            ])
+            ->log($inviato ? 'link_inviato' : 'link_non_inviato');
+
+        $numero = $assegnazione->territorio?->numero;
+        $nome = $assegnazione->proclamatore?->nome_completo;
+        $this->reset(['invioId', 'canaleUsato', 'erroreInvio']);
+
+        session()->flash('success', $inviato
+            ? "Territorio {$numero} assegnato a {$nome}: link inviato."
+            : "Territorio {$numero} assegnato a {$nome}. Il link è ancora da inviare: lo trovi segnalato nell'elenco.");
+        return $this->redirect($this->paginaDopoInvio(), navigate: true);
+    }
+
+    /** L'invio in corso, per la vista; null se l'assegnazione nel frattempo è rientrata o sparita. */
+    protected function invioCorrente(): ?Assegnazione
+    {
+        $invio = $this->invioId ? Assegnazione::aperte()->with(['territorio', 'proclamatore'])->find($this->invioId) : null;
+        if ($this->invioId && ! $invio) {
+            $this->reset(['invioId', 'canaleUsato', 'erroreInvio']);
+        }
+
+        return $invio;
+    }
+
+    private function assegnazioneInInvio(): ?Assegnazione
+    {
+        if (! $this->invioId) {
+            return null;
+        }
+
+        $assegnazione = Assegnazione::with(['territorio', 'proclamatore'])->find($this->invioId);
+        abort_unless($assegnazione && $this->puoInviare($assegnazione), 403);
+
+        return $assegnazione;
+    }
+}

app/Livewire/Concerns/RicordaRitorno.php

@@ -0,0 +1,33 @@
+<?php
+
+namespace App\Livewire\Concerns;
+
+use App\Support\Ritorno;
+use Livewire\Attributes\Locked;
+
+/**
+ * Per le pagine che si aprono da un'altra (schede e operazioni): ricorda da
+ * dove si è partiti (?da=…, vedi App\Support\Ritorno) e ci torna dopo la
+ * conferma. Annulla e "Torna…" nella vista usano $ritorno allo stesso modo.
+ *
+ * Aperta senza `da` (menu laterale, link salvato) la pagina si comporta come
+ * prima: ogni componente passa la sua destinazione predefinita.
+ */
+trait RicordaRitorno
+{
+    /** URL della pagina di partenza; null se aperta direttamente. */
+    #[Locked]
+    public ?string $ritorno = null;
+
+    /** Hook di Livewire: gira al mount di ogni componente che usa il trait. */
+    public function mountRicordaRitorno(): void
+    {
+        $this->ritorno = Ritorno::daRichiesta();
+    }
+
+    /** Dove andare dopo la conferma: la pagina di partenza, o quella predefinita. */
+    protected function destinazione(string $predefinita): string
+    {
+        return $this->ritorno ?? $predefinita;
+    }
+}

app/Livewire/Concerns/SegueOperazioneBackup.php

@@ -0,0 +1,318 @@
+<?php
+
+namespace App\Livewire\Concerns;
+
+use App\Services\BackupOperationState;
+use Illuminate\Support\Str;
+
+/**
+ * Parte comune ai componenti che avviano e seguono un'operazione lunga di
+ * backup: il posto unico, l'aggancio a quella in corso, il download automatico
+ * dell'archivio appena e' pronto, e le righe di log spedite alla console.
+ *
+ * Esiste perche' le operazioni sono avviate da due punti della pagina distanti
+ * fra loro — il backup dalla sua sezione, l'azzeramento dalla zona pericolosa in
+ * fondo — ma sono la stessa cosa vista dallo stesso stato condiviso. Duplicare
+ * postoLibero() significherebbe duplicare la regola su cui si regge il fatto che
+ * due operazioni non si sovrascrivano: e' l'ultimo posto dove ha senso avere due
+ * copie.
+ *
+ * Il resto dello stato vive in cache (BackupOperationState), non nel componente,
+ * quindi due componenti che seguono la stessa operazione restano coerenti senza
+ * doversi parlare.
+ */
+trait SegueOperazioneBackup
+{
+    /** Operazione seguita in questo momento; null quando non c'e' nulla in corso. */
+    public ?string $operationId = null;
+
+    public array $operazione = [];
+
+    /** Messaggio mostrato quando un avvio viene rifiutato. */
+    public string $erroreOperazione = '';
+
+    /**
+     * Quante righe di log sono gia' state spedite al browser.
+     *
+     * La console tiene il conto per conto suo, ma senza questo il componente
+     * rispedirebbe l'intera coda a ogni poll: la console la scarterebbe, ma
+     * intanto viaggerebbe dentro ogni risposta, sessanta righe alla volta,
+     * poco meno di due volte al secondo.
+     */
+    public int $logSpediti = 0;
+
+    /**
+     * Riaggancia l'operazione gia' in corso.
+     *
+     * Senza, ricaricare la pagina durante un backup lungo farebbe sparire ogni
+     * traccia, e un azzeramento fermo in attesa di conferma diventerebbe
+     * irraggiungibile: nessuno potrebbe piu' ne' confermarlo ne' annullarlo, e
+     * il posto resterebbe occupato fino alla scadenza.
+     */
+    protected function agganciaOperazioneCorrente(): void
+    {
+        $this->operationId = app(BackupOperationState::class)->corrente();
+        $this->logSpediti = 0;
+        $this->aggiorna();
+    }
+
+    public function aggiorna(): void
+    {
+        if (! $this->operationId) {
+            return;
+        }
+
+        $stato = app(BackupOperationState::class)->get($this->operationId);
+
+        if (! $stato) {
+            $this->operationId = null;
+            $this->operazione = [];
+            $this->logSpediti = 0;
+
+            return;
+        }
+
+        $this->operazione = $stato;
+
+        $this->spedisciAllaConsole();
+
+        // Il download parte da solo appena l'archivio e' pronto: per il backup
+        // e' una comodita', per l'azzeramento e' il passaggio che sblocca la
+        // cancellazione, quindi non puo' dipendere da un clic.
+        if ($this->scaricaOra()) {
+            $this->dispatch('scarica-backup', url: route('backup.file', $this->operationId));
+        }
+    }
+
+    /**
+     * Tipi di operazione che questo componente racconta alla console.
+     *
+     * Serve a stabilire un proprietario per ogni operazione. Backup e zona
+     * pericolosa seguono lo stesso stato condiviso, quindi senza questa
+     * distinzione entrambi spedirebbero le stesse righe e la console le
+     * mostrerebbe due volte — e a raddoppiare sarebbe anche il polling.
+     *
+     * @return array<int, string>
+     */
+    abstract protected function tipiSeguiti(): array;
+
+    protected function seguoQuestaOperazione(): bool
+    {
+        return in_array((string) ($this->operazione['tipo'] ?? ''), $this->tipiSeguiti(), true);
+    }
+
+    /**
+     * Manda alla console le righe nuove e lo stato di avanzamento.
+     *
+     * La console e' un componente Alpine fuori dal ciclo di Livewire (i suoi
+     * contenuti non possono essere ri-renderizzati dal server senza cancellare
+     * le righe scritte dal browser), quindi la comunicazione e' a eventi.
+     */
+    protected function spedisciAllaConsole(): void
+    {
+        // Chi non e' il proprietario tace: si aggiorna solo per sapere che il
+        // posto e' occupato e disabilitare i propri pulsanti.
+        if (! $this->seguoQuestaOperazione()) {
+            return;
+        }
+
+        $logs = $this->operazione['logs'] ?? [];
+
+        // Coda accorciata: e' un'operazione nuova, si riparte da capo.
+        if (count($logs) < $this->logSpediti) {
+            $this->logSpediti = 0;
+        }
+
+        $nuove = array_slice($logs, $this->logSpediti);
+        $this->logSpediti = count($logs);
+
+        $this->dispatch(
+            'console-operazione',
+            sorgente: $this->sorgenteConsole(),
+            righe: array_values($nuove),
+            etichetta: $this->etichettaOperazione(),
+            fase: (string) ($this->operazione['fase'] ?? ''),
+            percento: $this->percentuale,
+            stato: (string) ($this->operazione['status'] ?? ''),
+        );
+    }
+
+    protected function sorgenteConsole(): string
+    {
+        return match ($this->operazione['tipo'] ?? null) {
+            BackupOperationState::TIPO_BACKUP => 'backup',
+            BackupOperationState::TIPO_RESTORE => 'ripristino',
+            BackupOperationState::TIPO_RESET => 'azzeramento',
+            default => 'server',
+        };
+    }
+
+    protected function etichettaOperazione(): string
+    {
+        return match ($this->operazione['tipo'] ?? null) {
+            BackupOperationState::TIPO_BACKUP => 'Backup',
+            BackupOperationState::TIPO_RESTORE => 'Ripristino',
+            BackupOperationState::TIPO_RESET => 'Azzeramento',
+            default => '',
+        };
+    }
+
+    /**
+     * Vero se non c'e' gia' un'operazione in corso.
+     *
+     * Backup, ripristino e azzeramento lavorano tutti sullo stesso database e
+     * sullo stesso disco: farne partire due insieme — due schede, due
+     * amministratori — non li rallenta soltanto, li fa sovrascrivere a vicenda.
+     */
+    protected function postoLibero(): bool
+    {
+        $inCorso = app(BackupOperationState::class)->corrente();
+
+        if ($inCorso === null) {
+            $this->erroreOperazione = '';
+
+            return true;
+        }
+
+        $this->rifiutaPerOccupato($inCorso);
+
+        return false;
+    }
+
+    /**
+     * Si aggancia a quella in corso invece di limitarsi a rifiutare: chi ha
+     * premuto il pulsante vuole comunque vedere a che punto e'. Il messaggio
+     * dice quale operazione occupa il posto, perche' puo' essere un import
+     * avviato da un'altra zona della pagina, o da un altro amministratore.
+     */
+    private function rifiutaPerOccupato(string $inCorso): void
+    {
+        $this->operationId = $inCorso;
+        $this->logSpediti = 0;
+        $this->aggiorna();
+        $this->erroreOperazione = app(BackupOperationState::class)->messaggioOccupato($inCorso);
+    }
+
+    /**
+     * Prende il posto e crea l'operazione; null se il posto e' occupato.
+     *
+     * postoLibero() resta il controllo rapido prima di validare il resto, ma fra
+     * quel controllo e questo passo un'altra richiesta puo' arrivare prima — una
+     * seconda scheda, un import partito da un'altra zona. E' qui, sotto il mutex
+     * di BackupOperationState::occupa(), che si decide davvero.
+     */
+    protected function nuovaOperazione(string $tipo): ?string
+    {
+        $operationId = (string) Str::uuid();
+
+        $stato = app(BackupOperationState::class);
+        $inCorso = $stato->occupa($operationId, $tipo, 'In coda');
+
+        if ($inCorso !== null) {
+            $this->rifiutaPerOccupato($inCorso);
+
+            return null;
+        }
+
+        $stato->log($operationId, 'Operazione creata. In attesa del worker di coda.');
+
+        $this->logSpediti = 0;
+
+        return $operationId;
+    }
+
+    public function chiudi(): void
+    {
+        $this->operationId = null;
+        $this->operazione = [];
+        $this->logSpediti = 0;
+    }
+
+    /**
+     * True una volta sola per operazione: l'evento di download va emesso quando
+     * l'archivio compare, non a ogni poll successivo.
+     *
+     * Il segno che l'evento e' gia' partito sta nello stato condiviso, ed e'
+     * proprio per questo che solo il proprietario puo' arrivare fin qui: il
+     * componente che segue l'operazione di riflesso lo consumerebbe per primo —
+     * polla anche lui — spegnendo il download prima che il proprietario lo
+     * emetta. L'archivio sarebbe pronto e non arriverebbe a nessuno, e per
+     * l'azzeramento sarebbe pure il passo che sblocca la cancellazione.
+     */
+    private function scaricaOra(): bool
+    {
+        if (! $this->seguoQuestaOperazione()) {
+            return false;
+        }
+
+        $pronto = ($this->operazione['result']['file'] ?? null) !== null;
+        $giaInviato = $this->operazione['result']['download_inviato'] ?? false;
+
+        if (! $pronto || $giaInviato) {
+            return false;
+        }
+
+        app(BackupOperationState::class)->update($this->operationId, function (array $state) {
+            $state['result']['download_inviato'] = true;
+
+            return $state;
+        });
+
+        $this->operazione['result']['download_inviato'] = true;
+
+        return true;
+    }
+
+    /** Percentuale della fase corrente, 0-100. */
+    public function getPercentualeProperty(): int
+    {
+        if (($this->operazione['status'] ?? null) === 'completed') {
+            return 100;
+        }
+
+        $total = (int) ($this->operazione['total'] ?? 0);
+
+        if ($total <= 0) {
+            return 0;
+        }
+
+        return (int) min(100, round((int) ($this->operazione['processed'] ?? 0) / $total * 100));
+    }
+
+    /** Se true c'e' un'operazione aperta: i pulsanti di avvio restano disabilitati. */
+    public function getInCorsoProperty(): bool
+    {
+        return $this->operationId !== null
+            && in_array($this->operazione['status'] ?? '', ['queued', 'running'], true);
+    }
+
+    /**
+     * Ogni quanto reinterrogare lo stato.
+     *
+     * Tre regimi, per tre esigenze diverse:
+     *
+     * - 750ms per il proprietario mentre un job lavora: la barra deve muoversi e
+     *   le righe di log devono arrivare mentre succedono, non dopo.
+     * - 5s in attesa-download, dove si aspetta una persona che puo' metterci
+     *   minuti: bussare ogni 750ms vorrebbe dire migliaia di richieste inutili se
+     *   qualcuno lascia la scheda aperta e se ne va.
+     * - 3s per il componente che NON possiede l'operazione. Non ha righe da
+     *   raccontare, ma deve accorgersi che il posto si e' liberato: senza,
+     *   il suo pulsante resterebbe disabilitato fino al ricaricamento della
+     *   pagina, con l'aria di essersi rotto.
+     */
+    public function getIntervalloPollProperty(): string
+    {
+        if (! $this->seguoQuestaOperazione()) {
+            return '3s';
+        }
+
+        return $this->attesaDownload ? '5s' : '750ms';
+    }
+
+    /** Vero quando l'azzeramento ha l'archivio pronto e aspetta la conferma. */
+    public function getAttesaDownloadProperty(): bool
+    {
+        return ($this->operazione['fase'] ?? null) === BackupOperationState::FASE_ATTESA_DOWNLOAD;
+    }
+}

app/Livewire/Gruppi/GruppiIndex.php

@@ -0,0 +1,88 @@
+<?php
+
+namespace App\Livewire\Gruppi;
+
+use App\Livewire\Concerns\Avvisa;
+use App\Models\GruppoServizio;
+use App\Models\Proclamatore;
+use App\Services\GruppiServizio;
+use InvalidArgumentException;
+use Livewire\Attributes\Locked;
+use Livewire\Component;
+
+/**
+ * Gruppi di servizio (solo amministratore): elenco e creazione. Creando un
+ * gruppo si sceglie il sorvegliante, che riceve un'utenza con un'email
+ * fittizia ricavata dal suo nome (GruppiServizio::emailFittizia) e una
+ * password temporanea, mostrate qui una volta sola. Membri e pacchetto si
+ * gestiscono nella pagina del gruppo (GruppoShow).
+ */
+class GruppiIndex extends Component
+{
+    use Avvisa;
+
+    public string $nome = '';
+
+    public ?int $sorveglianteId = null;
+
+    /** Gruppo appena creato e password temporanea del sorvegliante, da consegnare. */
+    #[Locked]
+    public ?int $creatoId = null;
+
+    #[Locked]
+    public ?string $passwordTemporanea = null;
+
+    public function crea(): void
+    {
+        $this->authorize('settings.manage');
+
+        $this->validate([
+            'nome' => 'required|string|max:100|unique:gruppi_servizio,nome',
+            'sorveglianteId' => 'required|integer|exists:proclamatori,id',
+        ], [
+            'nome.unique' => 'Esiste già un gruppo con questo nome.',
+            'sorveglianteId.required' => 'Scegli il sorvegliante.',
+        ]);
+
+        try {
+            [$gruppo, $password] = app(GruppiServizio::class)->crea(
+                $this->nome,
+                Proclamatore::findOrFail($this->sorveglianteId),
+            );
+        } catch (InvalidArgumentException $e) {
+            $this->addError('sorveglianteId', $e->getMessage());
+
+            return;
+        }
+
+        $this->reset(['nome', 'sorveglianteId']);
+        $this->creatoId = $gruppo->id;
+        $this->passwordTemporanea = $password;
+    }
+
+    public function chiudiPassword(): void
+    {
+        $this->reset(['creatoId', 'passwordTemporanea']);
+    }
+
+    public function render()
+    {
+        $gruppi = GruppoServizio::with('sorvegliante')
+            ->withCount(['membri', 'territori'])
+            ->orderBy('nome')
+            ->get();
+
+        // Possono diventare sorveglianti i proclamatori attivi senza gruppo (e
+        // quindi senza utenza: sciolto il gruppo, la si elimina).
+        $candidati = Proclamatore::attivi()
+            ->whereNull('gruppo_servizio_id')
+            ->whereDoesntHave('utente')
+            ->get();
+
+        return view('livewire.gruppi.gruppi-index', [
+            'gruppi' => $gruppi,
+            'opzioniSorveglianti' => Proclamatore::opzioniScelta($candidati),
+            'creato' => $this->creatoId ? GruppoServizio::with('sorvegliante.utente')->find($this->creatoId) : null,
+        ]);
+    }
+}

app/Livewire/Gruppi/GruppoShow.php

@@ -0,0 +1,200 @@
+<?php
+
+namespace App\Livewire\Gruppi;
+
+use App\Livewire\Concerns\Avvisa;
+use App\Livewire\Concerns\RicordaRitorno;
+use App\Models\GruppoServizio;
+use App\Models\Proclamatore;
+use App\Models\Territorio;
+use App\Models\User;
+use App\Services\GruppiServizio;
+use Illuminate\Support\Str;
+use InvalidArgumentException;
+use Livewire\Attributes\Locked;
+use Livewire\Component;
+
+/**
+ * Un gruppo di servizio, lato amministratore: membri (aggiungere/togliere),
+ * pacchetto (aggiungere in blocco, rimandare in reparto quelli non dati),
+ * nuova password temporanea per il sorvegliante, scioglimento.
+ */
+class GruppoShow extends Component
+{
+    use Avvisa;
+    use RicordaRitorno;
+
+    public GruppoServizio $gruppo;
+
+    /** @var int[] proclamatori da aggiungere */
+    public array $nuoviMembri = [];
+
+    /** @var int[] territori da aggiungere al pacchetto */
+    public array $nuoviTerritori = [];
+
+    // Filtri dei territori in reparto da aggiungere al pacchetto. L'ordine è
+    // quello di priorità (Territorio::ordinaPerPriorita), come nella Home.
+    public string $cercaTerritorio = '';
+
+    public string $filtroZona = '';
+
+    public string $filtroTipologia = '';
+
+    public bool $soloPrioritari = false;
+
+    #[Locked]
+    public ?string $passwordTemporanea = null;
+
+    public function mount(GruppoServizio $gruppo): void
+    {
+        $this->gruppo = $gruppo;
+    }
+
+    private function servizio(): GruppiServizio
+    {
+        $this->authorize('settings.manage');
+
+        return app(GruppiServizio::class);
+    }
+
+    private function esegui(callable $azione, string $ok): void
+    {
+        try {
+            $azione();
+        } catch (InvalidArgumentException $e) {
+            $this->avvisaErrore($e->getMessage());
+
+            return;
+        }
+
+        $this->gruppo->refresh();
+        $this->avvisa($ok);
+    }
+
+    public function aggiungiMembri(): void
+    {
+        $ids = array_map('intval', $this->nuoviMembri);
+        if ($ids === []) {
+            $this->avvisaErrore('Spunta almeno un proclamatore.');
+
+            return;
+        }
+        $this->esegui(fn () => $this->servizio()->aggiungiMembri($this->gruppo, $ids), count($ids) . ' membri aggiunti.');
+        $this->nuoviMembri = [];
+    }
+
+    public function togliMembro(int $proclamatoreId): void
+    {
+        $membro = Proclamatore::findOrFail($proclamatoreId);
+        $this->esegui(fn () => $this->servizio()->togliMembro($this->gruppo, $membro), "{$membro->nome_completo} tolto dal gruppo.");
+    }
+
+    public function aggiungiTerritori(): void
+    {
+        $ids = array_map('intval', $this->nuoviTerritori);
+        if ($ids === []) {
+            $this->avvisaErrore('Spunta almeno un territorio.');
+
+            return;
+        }
+        $this->esegui(fn () => $this->servizio()->aggiungiAlPacchetto($this->gruppo, $ids), count($ids) . ' territori aggiunti al pacchetto.');
+        $this->nuoviTerritori = [];
+    }
+
+    /** Tutti i territori che i filtri mostrano finiscono tra quelli da aggiungere. */
+    public function selezionaMostrati(): void
+    {
+        $this->nuoviTerritori = collect($this->nuoviTerritori)
+            ->map(fn ($id) => (string) $id)
+            ->merge($this->candidatiFiltrati()->pluck('id')->map(fn ($id) => (string) $id))
+            ->unique()
+            ->values()
+            ->all();
+    }
+
+    public function deselezionaTutti(): void
+    {
+        $this->nuoviTerritori = [];
+    }
+
+    /** I territori in reparto, in ordine di priorità. */
+    private function candidati(): \Illuminate\Support\Collection
+    {
+        return Territorio::ordinaPerPriorita(
+            Territorio::inReparto()->with(['zona', 'tipologia', 'ultimaAssegnazione'])->get()
+        );
+    }
+
+    private function candidatiFiltrati(?\Illuminate\Support\Collection $candidati = null): \Illuminate\Support\Collection
+    {
+        $cerca = Str::lower(Str::ascii(trim($this->cercaTerritorio)));
+
+        return ($candidati ?? $this->candidati())
+            ->when($this->filtroZona !== '', fn ($c) => $c->where('zona_id', (int) $this->filtroZona))
+            ->when($this->filtroTipologia !== '', fn ($c) => $c->where('tipologia_id', (int) $this->filtroTipologia))
+            ->when($this->soloPrioritari, fn ($c) => $c->where('in_priorita', true))
+            ->when($cerca !== '', fn ($c) => $c->filter(fn (Territorio $t) => str_contains(
+                Str::lower(Str::ascii("{$t->numero} {$t->zona?->nome} {$t->tipologia?->nome}")),
+                $cerca
+            )))
+            ->values();
+    }
+
+    public function rimanda(int $territorioId): void
+    {
+        $territorio = Territorio::findOrFail($territorioId);
+        $this->esegui(fn () => $this->servizio()->rimandaInReparto($this->gruppo, $territorio), "Territorio {$territorio->numero} rimandato in reparto.");
+    }
+
+    /** Il sorvegliante ha perso la password: una nuova temporanea, da cambiare al primo accesso. */
+    public function nuovaPassword(): void
+    {
+        $this->servizio();
+        $utente = User::where('proclamatore_id', $this->gruppo->sorvegliante_id)->first();
+        if (! $utente) {
+            $this->avvisaErrore('Il gruppo non ha un sorvegliante con utenza attiva.');
+
+            return;
+        }
+
+        $this->passwordTemporanea = app(GruppiServizio::class)->nuovaPasswordTemporanea($utente);
+    }
+
+    /**
+     * Toglie il ruolo di sorvegliante: il gruppo si scioglie e si elimina, si
+     * torna all'elenco dei gruppi.
+     */
+    public function sciogli()
+    {
+        $nome = $this->gruppo->nome;
+        $this->servizio()->sciogli($this->gruppo);
+
+        session()->flash('success', "Gruppo {$nome} sciolto: i territori non ancora dati sono tornati in reparto e l'utenza del sorvegliante è stata eliminata.");
+        return $this->redirect(route('gruppi.index'), navigate: true);
+    }
+
+    public function render()
+    {
+        $this->gruppo->load(['sorvegliante.utente']);
+
+        $membri = $this->gruppo->membri()->get()->sortBy(fn ($p) => mb_strtolower($p->cognome . ' ' . $p->nome))->values();
+        $territori = $this->gruppo->territori()->with(['zona', 'assegnazioneCorrente.proclamatore'])->get()->sortBy('numero', SORT_NATURAL)->values();
+
+        // I territori in reparto (attivi, non assegnati, fuori da ogni
+        // pacchetto), in ordine di priorità; zone e tipologie dei filtri sono
+        // quelle che ci sono tra loro.
+        $candidati = $this->candidati();
+
+        return view('livewire.gruppi.gruppo-show', [
+            'membri' => $membri,
+            'territori' => $territori,
+            // Si possono aggiungere i proclamatori attivi senza gruppo...
+            'candidatiMembri' => Proclamatore::attivi()->whereNull('gruppo_servizio_id')->get()->sortBy(fn ($p) => mb_strtolower($p->cognome . ' ' . $p->nome))->values(),
+            // ...e i territori in reparto.
+            'totaleCandidati' => $candidati->count(),
+            'candidatiTerritori' => $this->candidatiFiltrati($candidati),
+            'zoneCandidati' => $candidati->filter(fn ($t) => $t->zona)->mapWithKeys(fn ($t) => [$t->zona_id => $t->zona->nome])->sort(),
+            'tipologieCandidati' => $candidati->filter(fn ($t) => $t->tipologia)->mapWithKeys(fn ($t) => [$t->tipologia_id => $t->tipologia->nome])->sort(),
+        ]);
+    }
+}

app/Livewire/Gruppi/MioGruppo.php

@@ -0,0 +1,227 @@
+<?php
+
+namespace App\Livewire\Gruppi;
+
+use App\Livewire\Concerns\Avvisa;
+use App\Livewire\Concerns\InviaLink;
+use App\Models\Assegnazione;
+use App\Models\GruppoServizio;
+use App\Models\Proclamatore;
+use App\Models\Territorio;
+use App\Services\GruppiServizio;
+use Carbon\Carbon;
+use InvalidArgumentException;
+use Livewire\Attributes\Locked;
+use Livewire\Attributes\Url;
+use Livewire\Component;
+
+/**
+ * "Il mio gruppo": la sola pagina del sorvegliante di gruppo. Vede il
+ * pacchetto del suo gruppo e i membri; dà i territori ai membri (o a sé),
+ * manda il link, registra i rientri (pagina Rientra), apre la piantina e
+ * rimanda in reparto quelli non ancora dati. Le regole stanno in
+ * App\Services\GruppiServizio; qui ogni azione ricontrolla che il territorio
+ * o l'assegnazione siano del suo gruppo.
+ */
+class MioGruppo extends Component
+{
+    use Avvisa;
+    use InviaLink;
+
+    /** Il territorio del pacchetto che si sta assegnando. */
+    #[Locked]
+    public ?int $territorioDaAssegnare = null;
+
+    public ?int $membroId = null;
+
+    public string $dataAssegnazione = '';
+
+    /** Il membro ha chiesto la cartolina cartacea (elenco Cartacei). */
+    public bool $cartaceo = false;
+
+    // Filtri del pacchetto, nell'indirizzo: tornando dal rientro si ritrovano.
+    #[Url(except: '')]
+    public string $filtroZona = '';
+
+    #[Url(except: '')]
+    public string $filtroTipologia = '';
+
+    /** '' tutti, 'da_dare', 'dati' */
+    #[Url(except: '')]
+    public string $filtroStato = '';
+
+    #[Url(except: false)]
+    public bool $soloPrioritari = false;
+
+    public function mount(): void
+    {
+        $this->dataAssegnazione = now()->format('Y-m-d');
+    }
+
+    private function gruppo(): ?GruppoServizio
+    {
+        return auth()->user()->gruppoSorvegliato();
+    }
+
+    private function gruppoOFallisci(): GruppoServizio
+    {
+        $gruppo = $this->gruppo();
+        abort_unless($gruppo, 403, 'Non sei il sorvegliante di un gruppo di servizio attivo.');
+
+        return $gruppo;
+    }
+
+    private function territorioDelPacchetto(int $id): Territorio
+    {
+        $gruppo = $this->gruppoOFallisci();
+        $territorio = Territorio::find($id);
+        abort_unless($territorio && $territorio->gruppo_servizio_id === $gruppo->id, 403);
+
+        return $territorio;
+    }
+
+    // ─── Assegnare un territorio del pacchetto ──────────────────
+
+    public function apriAssegnazione(int $territorioId): void
+    {
+        $this->territorioDelPacchetto($territorioId);
+        $this->territorioDaAssegnare = $territorioId;
+        $this->membroId = null;
+        $this->cartaceo = false;
+        $this->dataAssegnazione = now()->format('Y-m-d');
+        $this->resetValidation();
+    }
+
+    public function annullaAssegnazione(): void
+    {
+        $this->reset(['territorioDaAssegnare', 'membroId', 'cartaceo']);
+        $this->resetValidation();
+    }
+
+    public function assegna(): void
+    {
+        $this->validate([
+            'membroId' => 'required|integer',
+            'dataAssegnazione' => 'required|date|before_or_equal:today',
+        ], [
+            'membroId.required' => 'Scegli a chi dare il territorio.',
+            'dataAssegnazione.before_or_equal' => 'La data non può essere nel futuro.',
+        ]);
+
+        $gruppo = $this->gruppoOFallisci();
+        $territorio = $this->territorioDelPacchetto((int) $this->territorioDaAssegnare);
+        $membro = Proclamatore::find($this->membroId);
+
+        if (! $membro) {
+            $this->addError('membroId', 'Scegli un membro del gruppo.');
+
+            return;
+        }
+
+        try {
+            $assegnazione = app(GruppiServizio::class)->assegna($gruppo, $territorio, $membro, Carbon::parse($this->dataAssegnazione), $this->cartaceo);
+        } catch (InvalidArgumentException $e) {
+            $this->addError('membroId', $e->getMessage());
+
+            return;
+        }
+
+        $this->reset(['territorioDaAssegnare', 'membroId', 'cartaceo']);
+
+        // Come dalla pagina Assegna: si apre l'invio del link.
+        $this->apriInvio($assegnazione->id);
+    }
+
+    // ─── Rimandare in reparto ───────────────────────────────────
+
+    public function rimanda(int $territorioId): void
+    {
+        $territorio = $this->territorioDelPacchetto($territorioId);
+
+        try {
+            app(GruppiServizio::class)->rimandaInReparto($this->gruppoOFallisci(), $territorio);
+        } catch (InvalidArgumentException $e) {
+            $this->avvisaErrore($e->getMessage());
+
+            return;
+        }
+
+        $this->avvisa("Territorio {$territorio->numero} rimandato in reparto.");
+    }
+
+    // ─── Link già inviato / condiviso dall'elenco ───────────────
+
+    private function assegnazioneDelGruppo(int $id): Assegnazione
+    {
+        $assegnazione = Assegnazione::aperte()->with('territorio')->find($id);
+        abort_unless($assegnazione && $this->puoInviare($assegnazione), 403);
+
+        return $assegnazione;
+    }
+
+    public function toggleLinkSent(int $assegnazioneId): void
+    {
+        $assegnazione = $this->assegnazioneDelGruppo($assegnazioneId);
+        $assegnazione->registraInvioLink(! $assegnazione->link_sent, $assegnazione->link_canale);
+    }
+
+    /** "Condividi" dall'elenco andato a buon fine (elencoCercabile.condividi). */
+    public function segnaCondiviso(int $assegnazioneId): void
+    {
+        $this->assegnazioneDelGruppo($assegnazioneId)->registraInvioLink(true, 'condividi');
+    }
+
+    // ─── Invio del link (trait InviaLink) ───────────────────────
+
+    protected function puoInviare(Assegnazione $assegnazione): bool
+    {
+        $gruppo = $this->gruppo();
+
+        return $gruppo !== null
+            && ($assegnazione->gruppo_servizio_id === $gruppo->id
+                || $assegnazione->territorio?->gruppo_servizio_id === $gruppo->id);
+    }
+
+    protected function paginaDopoInvio(): string
+    {
+        return route('mio-gruppo');
+    }
+
+    public function render()
+    {
+        $gruppo = $this->gruppo()?->load('sorvegliante');
+
+        // Prima quelli da dare, in ordine di priorità come "Da assegnare"
+        // nella Home (Territorio::ordinaPerPriorita); poi quelli già dati, dal
+        // più vecchio.
+        $pacchetto = $gruppo
+            ? $gruppo->territori()->with(['zona', 'tipologia', 'ultimaAssegnazione', 'assegnazioneCorrente.proclamatore'])->get()
+            : collect();
+        [$dati, $daDare] = $pacchetto->partition(fn (Territorio $t) => $t->assegnazioneCorrente !== null);
+        $pacchetto = Territorio::ordinaPerPriorita($daDare)
+            ->concat($dati->sortBy(fn (Territorio $t) => $t->assegnazioneCorrente->assigned_at)->values());
+
+        $territori = $pacchetto
+            ->when($this->filtroZona !== '', fn ($c) => $c->where('zona_id', (int) $this->filtroZona))
+            ->when($this->filtroTipologia !== '', fn ($c) => $c->where('tipologia_id', (int) $this->filtroTipologia))
+            ->when($this->filtroStato === 'da_dare', fn ($c) => $c->whereNull('assegnazioneCorrente'))
+            ->when($this->filtroStato === 'dati', fn ($c) => $c->whereNotNull('assegnazioneCorrente'))
+            ->when($this->soloPrioritari, fn ($c) => $c->where('in_priorita', true))
+            ->values();
+
+        $membri = $gruppo
+            ? $gruppo->membri()->where('attivo', true)->get()->sortBy(fn ($p) => mb_strtolower($p->cognome . ' ' . $p->nome))->values()
+            : collect();
+
+        return view('livewire.gruppi.mio-gruppo', [
+            'gruppo' => $gruppo,
+            'pacchetto' => $pacchetto,
+            'territori' => $territori,
+            'zone' => $pacchetto->filter(fn ($t) => $t->zona)->mapWithKeys(fn ($t) => [$t->zona_id => $t->zona->nome])->sort(),
+            'tipologie' => $pacchetto->filter(fn ($t) => $t->tipologia)->mapWithKeys(fn ($t) => [$t->tipologia_id => $t->tipologia->nome])->sort(),
+            'membri' => $membri,
+            'opzioniMembri' => Proclamatore::opzioniScelta($membri, conGruppo: false),
+            'invio' => $this->invioCorrente(),
+        ]);
+    }
+}

app/Livewire/Home.php

@@ -3,50 +3,67 @@
 namespace App\Livewire;
 
 use Livewire\Component;
+use App\Livewire\Concerns\Avvisa;
 use App\Models\Territorio;
 use App\Models\Proclamatore;
 use App\Models\Assegnazione;
 use App\Models\AnnoTeocratico;
 use App\Models\Campagna;
+use App\Models\Richiesta;
 use App\Models\Setting;
+use App\Services\RichiesteServizio;
 use Barryvdh\DomPDF\Facade\Pdf;
 
 class Home extends Component
 {
+    use Avvisa;
+
+    /**
+     * Le richieste dal modulo pubblico si confermano portandole su Assegna o
+     * Rientra (link nel riquadro); qui si possono solo scartare.
+     */
+    public function scartaRichiesta(int $id): void
+    {
+        $this->authorize('richieste.gestisci');
+        Richiesta::findOrFail($id)->scarta(auth()->user());
+        $this->avvisa('Richiesta scartata.');
+    }
+
+    /**
+     * Le richieste aperte, con quello che serve a confermarle: per un
+     * territorio nuovo i proclamatori dal nome simile a quello scritto, per
+     * una riconsegna l'assegnazione aperta di quel territorio.
+     */
+    private function richiesteAperte(): \Illuminate\Support\Collection
+    {
+        if (! auth()->user()->can('richieste.gestisci')) {
+            return collect();
+        }
+
+        $aperte = Richiesta::aperte()->orderBy('created_at')->get();
+        if ($aperte->isEmpty()) {
+            return collect();
+        }
+
+        $servizio = app(RichiesteServizio::class);
+        $proclamatori = Proclamatore::attivi()->get();
+
+        return $aperte->map(fn (Richiesta $r) => [
+            'richiesta' => $r,
+            'simili' => $r->tipo === Richiesta::NUOVO ? $servizio->nomiSimili($r->nome, $proclamatori) : collect(),
+            'assegnazione' => $r->tipo === Richiesta::RICONSEGNA ? $servizio->assegnazioneAperta($r->numero_territorio) : null,
+        ]);
+    }
+
     public function downloadPdfDaAssegnare()
     {
         $this->authorize('territori.assign');
 
         $settings = Setting::instance();
-        $priorityThreshold = (int) ($settings->giorni_giacenza_prioritari ?? 180);
 
-        $territori = Territorio::inReparto()
-            ->with('zona', 'tipologia', 'ultimaAssegnazione')
-            ->get()
-            ->map(function (Territorio $territorio) use ($priorityThreshold) {
-                $ultima = $territorio->ultimaAssegnazione;
-                if ($ultima && $ultima->returned_at) {
-                    $giorniGiacenza = $ultima->returned_at->startOfDay()->diffInDays(today());
-                } elseif (! $ultima) {
-                    $giorniGiacenza = $territorio->created_at->startOfDay()->diffInDays(today());
-                } else {
-                    $giorniGiacenza = 0;
-                }
-                $territorio->setAttribute('home_giorni_giacenza', $giorniGiacenza);
-                $territorio->setAttribute(
-                    'home_is_prioritario',
-                    (bool) $territorio->prioritario || $giorniGiacenza > $priorityThreshold
-                );
-                return $territorio;
-            })
-            ->sort(function (Territorio $left, Territorio $right) {
-                $p = (int) $right->home_is_prioritario <=> (int) $left->home_is_prioritario;
-                if ($p !== 0) return $p;
-                $g = $right->home_giorni_giacenza <=> $left->home_giorni_giacenza;
-                if ($g !== 0) return $g;
-                return strnatcasecmp((string) $left->numero, (string) $right->numero);
-            })
-            ->values();
+        $territori = Territorio::ordinaPerPriorita(
+            Territorio::inReparto()->with('zona', 'tipologia', 'ultimaAssegnazione')->get()
+        );
 
         $pdf = Pdf::loadView('pdf.territori-lista', [
             'titolo' => 'Territori da Assegnare',
@@ -90,7 +107,6 @@ class Home extends Component
     {
         $settings = Setting::instance();
         $homeLimit = max(1, (int) ($settings->home_limit_list ?? 10));
-        $priorityThreshold = (int) ($settings->giorni_giacenza_prioritari ?? 180);
         $annoCorrente = AnnoTeocratico::corrente();
         $campagnaAttiva = Campagna::attiva();
 
@@ -115,14 +131,27 @@ class Home extends Component
         }
 
         // Average assignment duration in months (current year only, matches old app "Media Percorrenza Congregazione")
+        //
+        // Il calcolo sta in PHP e non in SQL. La versione precedente usava
+        // DATEDIFF() e YEAR(), che sono funzioni MySQL: rendevano questa pagina
+        // — la piu' visitata dell'applicazione — l'unica non verificabile dalla
+        // suite di test, che gira su SQLite. Il costo e' due colonne di date per
+        // le assegnazioni chiuse di un anno di servizio: qualche centinaio di
+        // righe, non un tavolo intero.
+        //
+        // I due filtri sono quelli di prima: le date assurde arrivate dalla
+        // conversione del vecchio database, e le durate non positive, che
+        // altrimenti abbasserebbero la media senza significare niente.
         $avgGiorni = null;
         if ($annoCorrente) {
-            $avgGiorni = Assegnazione::where('anno_teocratico_id', $annoCorrente->id)
+            $durate = Assegnazione::where('anno_teocratico_id', $annoCorrente->id)
                 ->whereNotNull('returned_at')
-                ->whereRaw('YEAR(assigned_at) >= 1900')
-                ->whereRaw('DATEDIFF(returned_at, assigned_at) > 0')
-                ->selectRaw('AVG(DATEDIFF(returned_at, assigned_at)) as media_giorni')
-                ->value('media_giorni');
+                ->get(['assigned_at', 'returned_at'])
+                ->filter(fn (Assegnazione $a) => $a->assigned_at?->year >= 1900)
+                ->map(fn (Assegnazione $a) => $a->assigned_at->diffInDays($a->returned_at, false))
+                ->filter(fn (float $giorni) => $giorni > 0);
+
+            $avgGiorni = $durate->isEmpty() ? null : $durate->avg();
         }
         $mediaDurataPercorrenzaMesi = $avgGiorni ? round($avgGiorni / 30.44, 1) : 0;
 
@@ -136,46 +165,11 @@ class Home extends Component
             ];
         }
 
-        // Quick lists
-        $territoriDaAssegnare = Territorio::inReparto()
-            ->with('zona', 'tipologia', 'ultimaAssegnazione')
-            ->get()
-            ->map(function (Territorio $territorio) use ($priorityThreshold) {
-                $ultima = $territorio->ultimaAssegnazione;
-
-                if ($ultima && $ultima->returned_at) {
-                    $giorniGiacenza = $ultima->returned_at->startOfDay()->diffInDays(today());
-                } elseif (! $ultima) {
-                    $giorniGiacenza = $territorio->created_at->startOfDay()->diffInDays(today());
-                } else {
-                    $giorniGiacenza = 0;
-                }
-
-                $territorio->setAttribute('home_giorni_giacenza', $giorniGiacenza);
-                $territorio->setAttribute(
-                    'home_is_prioritario',
-                    (bool) $territorio->prioritario || $giorniGiacenza > $priorityThreshold
-                );
-
-                return $territorio;
-            })
-            ->sort(function (Territorio $left, Territorio $right) {
-                $priorityComparison = (int) $right->home_is_prioritario <=> (int) $left->home_is_prioritario;
-
-                if ($priorityComparison !== 0) {
-                    return $priorityComparison;
-                }
-
-                $giacenzaComparison = $right->home_giorni_giacenza <=> $left->home_giorni_giacenza;
-
-                if ($giacenzaComparison !== 0) {
-                    return $giacenzaComparison;
-                }
-
-                return strnatcasecmp((string) $left->numero, (string) $right->numero);
-            })
-            ->take($homeLimit)
-            ->values();
+        // Quick lists: la logica di priorità sta in Territorio::ordinaPerPriorita
+        // (la usano anche il pacchetto dei gruppi di servizio e "Il mio gruppo").
+        $territoriDaAssegnare = Territorio::ordinaPerPriorita(
+            Territorio::inReparto()->with('zona', 'tipologia', 'ultimaAssegnazione')->get()
+        )->take($homeLimit)->values();
 
         $daRientrare = Territorio::daRientrare()
             ->with(['zona', 'assegnazioneCorrente.proclamatore'])
@@ -195,6 +189,7 @@ class Home extends Component
             'homeLimit' => $homeLimit,
             'territoriDaAssegnare' => $territoriDaAssegnare,
             'daRientrare' => $daRientrare,
+            'richieste' => $this->richiesteAperte(),
         ]);
     }
 }

app/Livewire/Piantine/PiantineEditor.php

@@ -0,0 +1,612 @@
+<?php
+
+namespace App\Livewire\Piantine;
+
+use App\Livewire\Concerns\Avvisa;
+use App\Models\Territorio;
+use App\Models\TerritorioMappa;
+use App\Models\Tipologia;
+use App\Models\Zona;
+use App\Services\Piantine\PiantineArea;
+use Illuminate\Support\Facades\DB;
+use Illuminate\Support\Facades\Storage;
+use Illuminate\Validation\Rule;
+use Livewire\Attributes\Layout;
+use Livewire\Attributes\Locked;
+use Livewire\Attributes\On;
+use Livewire\Component;
+
+/**
+ * Editor delle piantine a schermo intero (solo amministratore).
+ *
+ * Tutto quello che si fa qui è bozza e si salva da solo: il confine a ogni
+ * disegno o spostamento di vertice, il nome e il collegamento appena cambiano.
+ * La bozza non tocca il PDF del territorio, che cambia solo con "Pubblica"
+ * (anteprima e conferma, nel componente Pubblicazione). I dati del territorio
+ * — numero, zona, tipologia, confini — sono invece dati del gestionale e si
+ * salvano subito, come dalla scheda territorio.
+ *
+ * Disegnare crea sempre una piantina nuova: per cambiare il confine di quella
+ * aperta ci sono "Modifica vertici" e "Ridisegna", espliciti. Prima un
+ * disegno fatto con una piantina aperta ne sostituiva il confine in silenzio.
+ *
+ * Con la mappa si parla per eventi, e solo con il necessario: i dati di tutte
+ * le piantine li chiede la mappa una volta (datiMappa), poi riceve solo la
+ * piantina cambiata. Prima ogni richiesta rispediva tutte le geometrie e
+ * l'area KML, fino a una decina di MB per aprire un pannello.
+ */
+#[Layout('components.layouts.editor')]
+class PiantineEditor extends Component
+{
+    use Avvisa;
+
+    /** Piantina aperta, o null quando non ce n'è nessuna selezionata. */
+    #[Locked]
+    public ?int $mappaId = null;
+
+    public string $nome = '';
+
+    /** Ora dell'ultimo salvataggio automatico, per l'indicazione in testata. */
+    public string $salvatoAlle = '';
+
+    // ─── Territorio ─────────────────────────────────────────────────────────
+
+    /** '' = nessun territorio, 'nuovo' = da creare, altrimenti l'id. */
+    public string $territorioScelto = '';
+
+    public string $numero = '';
+
+    public string $zonaId = '';
+
+    public string $tipologiaId = '';
+
+    public string $confini = '';
+
+    public string $nuovaZona = '';
+
+    public string $nuovaTipologia = '';
+
+    /**
+     * Arrivati da "Nuovo territorio" (?nuovo=1): la mappa parte già in
+     * disegno, e la prima piantina disegnata si apre con "nuovo territorio"
+     * scelto, pronta da compilare e creare.
+     */
+    #[Locked]
+    public bool $creaTerritorio = false;
+
+    public function mount(?int $mappa = null): void
+    {
+        if ($mappa !== null && TerritorioMappa::whereKey($mappa)->exists()) {
+            $this->carica(TerritorioMappa::with('territorio')->find($mappa));
+        } elseif (request()->boolean('nuovo')) {
+            $this->creaTerritorio = true;
+        }
+    }
+
+    // ─── Selezione ──────────────────────────────────────────────────────────
+
+    #[On('piantina-selezionata-mappa')]
+    public function apri($mappaId): void
+    {
+        $mappa = TerritorioMappa::with('territorio')->find(is_numeric($mappaId) ? (int) $mappaId : null);
+
+        if (! $mappa) {
+            $this->avvisaErrore('Questa piantina non esiste più: forse è stata eliminata da un\'altra scheda.');
+            $this->dispatch('piantina-rimossa', mappaId: (int) $mappaId);
+
+            return;
+        }
+
+        $this->carica($mappa);
+        $this->dispatch('piantina-selezionata', mappaId: $mappa->id, inquadra: true);
+    }
+
+    /** "Nuova piantina": si deseleziona e la mappa entra in modalità disegno. */
+    public function nuova(): void
+    {
+        $this->svuota();
+        $this->dispatch('piantina-selezionata', mappaId: null, inquadra: false);
+        $this->dispatch('editor-disegna');
+    }
+
+    private function carica(TerritorioMappa $mappa): void
+    {
+        $this->resetValidation();
+        $this->mappaId = $mappa->id;
+        $this->nome = (string) $mappa->nome;
+        $this->salvatoAlle = '';
+        $this->nuovaZona = '';
+        $this->nuovaTipologia = '';
+        $this->caricaTerritorio($mappa->territorio);
+    }
+
+    private function svuota(): void
+    {
+        $this->resetValidation();
+        $this->reset([
+            'mappaId', 'nome', 'salvatoAlle',
+            'territorioScelto', 'numero', 'zonaId', 'tipologiaId', 'confini',
+            'nuovaZona', 'nuovaTipologia',
+        ]);
+    }
+
+    private function caricaTerritorio(?Territorio $territorio): void
+    {
+        $this->territorioScelto = $territorio ? (string) $territorio->id : '';
+        $this->numero = (string) ($territorio->numero ?? '');
+        $this->zonaId = (string) ($territorio->zona_id ?? '');
+        $this->tipologiaId = (string) ($territorio->tipologia_id ?? '');
+        $this->confini = (string) ($territorio->confini ?? '');
+    }
+
+    // ─── Confine (bozza, salvataggio automatico) ────────────────────────────
+
+    /**
+     * Arriva dalla mappa dopo un disegno o lo spostamento di un vertice.
+     * $nuova: il disegno è una piantina nuova (strumento "Disegna"), non il
+     * confine ridisegnato di quella aperta.
+     */
+    #[On('geometria-modificata')]
+    public function salvaGeometria($geometry, bool $nuova = false): void
+    {
+        if (! $this->geometriaValida($geometry)) {
+            $this->avvisaErrore('Il confine disegnato non è valido: ridisegnalo.');
+
+            return;
+        }
+
+        $geojson = json_encode($geometry);
+        $mappa = (! $nuova && $this->mappaId) ? TerritorioMappa::find($this->mappaId) : null;
+
+        if ($mappa) {
+            $mappa->update(['geojson' => $geojson]);
+        } else {
+            $mappa = TerritorioMappa::create(['geojson' => $geojson]);
+            $this->carica($mappa);
+            activity()->causedBy(auth()->user())->log('piantina_creata');
+
+            if ($this->creaTerritorio) {
+                $this->creaTerritorio = false;
+                $this->territorioScelto = 'nuovo';
+            }
+        }
+
+        $this->salvato($mappa, seleziona: true);
+    }
+
+    /**
+     * Anelli chiusi di almeno quattro punti con coordinate nei limiti: un
+     * record malformato faceva fallire il disegno di tutte le piantine.
+     */
+    private function geometriaValida($geometry): bool
+    {
+        if (! is_array($geometry) || ! is_array($geometry['coordinates'] ?? null)) {
+            return false;
+        }
+
+        $poligoni = match ($geometry['type'] ?? null) {
+            'Polygon' => [$geometry['coordinates']],
+            'MultiPolygon' => $geometry['coordinates'],
+            default => null,
+        };
+
+        if (! $poligoni) {
+            return false;
+        }
+
+        foreach ($poligoni as $anelli) {
+            if (! is_array($anelli) || $anelli === []) {
+                return false;
+            }
+            foreach ($anelli as $anello) {
+                if (! is_array($anello) || count($anello) < 4) {
+                    return false;
+                }
+                foreach ($anello as $punto) {
+                    if (! is_array($punto) || count($punto) < 2
+                        || ! is_numeric($punto[0]) || ! is_numeric($punto[1])
+                        || abs($punto[0]) > 180 || abs($punto[1]) > 90) {
+                        return false;
+                    }
+                }
+            }
+        }
+
+        return true;
+    }
+
+    /** Riporta il confine a quello pubblicato. */
+    public function scartaModifiche(): void
+    {
+        $mappa = $this->mappaAperta();
+
+        if (! $mappa || ! $mappa->bozzaScartabile()) {
+            return;
+        }
+
+        $mappa->update(['geojson' => $mappa->geojson_pubblicato]);
+        $this->salvato($mappa, seleziona: true);
+        $this->avvisa('Confine riportato a quello pubblicato.');
+    }
+
+    public function updatedNome(): void
+    {
+        $mappa = $this->mappaAperta();
+
+        if (! $mappa) {
+            return;
+        }
+
+        $nome = trim($this->nome);
+        $mappa->update(['nome' => $nome !== '' ? mb_substr($nome, 0, 120) : null]);
+        $this->salvato($mappa);
+    }
+
+    // ─── Collegamento al territorio ─────────────────────────────────────────
+
+    public function updatedTerritorioScelto(string $valore): void
+    {
+        $this->resetValidation();
+        $mappa = $this->mappaAperta();
+
+        if (! $mappa) {
+            return;
+        }
+
+        if ($valore === 'nuovo') {
+            // Si compilano i campi e si crea con il pulsante: un territorio
+            // non nasce da un salvataggio automatico a metà digitazione.
+            $this->numero = '';
+            $this->zonaId = '';
+            $this->tipologiaId = '';
+            $this->confini = '';
+
+            return;
+        }
+
+        if ($valore === '') {
+            $numero = $mappa->territorio?->numero;
+            $mappa->update([
+                'territorio_id' => null,
+                // Senza territorio serve un'etichetta, altrimenti la piantina
+                // finisce in elenco come un anonimo "Piantina #12".
+                'nome' => $mappa->nome ?: ($numero ? "Ex territorio {$numero}" : null),
+            ]);
+            $this->nome = (string) $mappa->nome;
+            $this->caricaTerritorio(null);
+            $this->salvato($mappa);
+
+            return;
+        }
+
+        $territorio = Territorio::find($valore);
+        if (! $territorio) {
+            $this->addError('territorioScelto', 'Il territorio scelto non esiste più.');
+            $this->caricaTerritorio($mappa->territorio);
+
+            return;
+        }
+
+        $occupata = TerritorioMappa::where('territorio_id', $territorio->id)->whereKeyNot($mappa->id)->exists();
+        if ($occupata) {
+            $this->addError('territorioScelto', "Il territorio {$territorio->numero} ha già una piantina.");
+            $this->caricaTerritorio($mappa->territorio);
+
+            return;
+        }
+
+        $mappa->update(['territorio_id' => $territorio->id]);
+        $this->caricaTerritorio($territorio);
+        activity()->causedBy(auth()->user())->performedOn($territorio)->log('piantina_collegata');
+        $this->salvato($mappa);
+    }
+
+    public function creaTerritorio(): void
+    {
+        $mappa = $this->mappaAperta();
+
+        if (! $mappa || $this->territorioScelto !== 'nuovo') {
+            return;
+        }
+
+        $this->numero = trim($this->numero);
+        $this->confini = trim($this->confini);
+
+        $this->validate(
+            [
+                'numero' => ['required', 'string', 'max:20', Rule::unique('territori', 'numero')],
+                'zonaId' => ['nullable', Rule::exists('zone', 'id')],
+                'tipologiaId' => ['nullable', Rule::exists('tipologie', 'id')],
+                'confini' => ['nullable', 'string', 'max:5000'],
+            ],
+            $this->messaggiTerritorio(),
+        );
+
+        try {
+            $territorio = DB::transaction(function () use ($mappa) {
+                $territorio = Territorio::create($this->valoriTerritorio() + ['attivo' => true]);
+                $mappa->update(['territorio_id' => $territorio->id]);
+
+                return $territorio;
+            });
+        } catch (\Illuminate\Database\UniqueConstraintViolationException) {
+            $this->addError('numero', 'Esiste già un territorio con questo numero.');
+
+            return;
+        }
+
+        activity()->causedBy(auth()->user())->performedOn($territorio)->log('territorio_creato_da_piantine');
+
+        $this->caricaTerritorio($territorio);
+        $this->salvato($mappa);
+        $this->avvisa("Territorio {$territorio->numero} creato e collegato.");
+    }
+
+    // ─── Dati del territorio (salvati subito nel gestionale) ────────────────
+
+    public function updatedNumero(): void
+    {
+        $this->salvaCampoTerritorio('numero');
+    }
+
+    public function updatedZonaId(): void
+    {
+        $this->salvaCampoTerritorio('zonaId');
+    }
+
+    public function updatedTipologiaId(): void
+    {
+        $this->salvaCampoTerritorio('tipologiaId');
+    }
+
+    public function updatedConfini(): void
+    {
+        $this->salvaCampoTerritorio('confini');
+    }
+
+    private function salvaCampoTerritorio(string $campo): void
+    {
+        // In creazione i campi si raccolgono e basta: li salva creaTerritorio().
+        $territorio = $this->territorioCollegato();
+        if (! $territorio) {
+            return;
+        }
+
+        $this->numero = trim($this->numero);
+
+        $regole = [
+            'numero' => ['required', 'string', 'max:20', Rule::unique('territori', 'numero')->ignore($territorio->id)],
+            'zonaId' => ['nullable', Rule::exists('zone', 'id')],
+            'tipologiaId' => ['nullable', Rule::exists('tipologie', 'id')],
+            'confini' => ['nullable', 'string', 'max:5000'],
+        ];
+
+        $this->validateOnly($campo, $regole, $this->messaggiTerritorio());
+
+        // Solo la colonna del campo cambiato: con un altro campo ancora non
+        // valido a schermo, riscrivere tutto salverebbe anche quel valore.
+        $colonna = ['numero' => 'numero', 'zonaId' => 'zona_id', 'tipologiaId' => 'tipologia_id', 'confini' => 'confini'][$campo];
+        $territorio->update([$colonna => $this->valoriTerritorio()[$colonna]]);
+
+        $this->salvato($this->mappaAperta());
+    }
+
+    private function valoriTerritorio(): array
+    {
+        return [
+            'numero' => trim($this->numero),
+            'zona_id' => $this->zonaId !== '' ? (int) $this->zonaId : null,
+            'tipologia_id' => $this->tipologiaId !== '' ? (int) $this->tipologiaId : null,
+            'confini' => trim($this->confini) !== '' ? trim($this->confini) : null,
+        ];
+    }
+
+    private function messaggiTerritorio(): array
+    {
+        return [
+            'numero.required' => 'Il territorio ha bisogno di un numero.',
+            'numero.unique' => 'Esiste già un territorio con questo numero.',
+            'numero.max' => 'Il numero può avere al massimo 20 caratteri.',
+            'confini.max' => 'I confini possono avere al massimo 5000 caratteri.',
+        ];
+    }
+
+    // ─── Zona e tipologia create sul posto ──────────────────────────────────
+
+    public function creaZona(): void
+    {
+        $this->nuovaZona = trim($this->nuovaZona);
+        $dati = $this->validate(
+            ['nuovaZona' => ['required', 'string', 'max:100', Rule::unique('zone', 'nome')]],
+            [
+                'nuovaZona.required' => 'Scrivi il nome della zona.',
+                'nuovaZona.unique' => 'Questa zona esiste già: sceglila dall\'elenco.',
+            ],
+        );
+
+        $zona = Zona::create(['nome' => $dati['nuovaZona'], 'attivo' => true]);
+
+        $this->zonaId = (string) $zona->id;
+        $this->nuovaZona = '';
+        $this->updatedZonaId();
+        $this->avvisa("Zona «{$zona->nome}» creata e selezionata.");
+    }
+
+    public function creaTipologia(): void
+    {
+        $this->nuovaTipologia = trim($this->nuovaTipologia);
+        $dati = $this->validate(
+            ['nuovaTipologia' => ['required', 'string', 'max:100', Rule::unique('tipologie', 'nome')]],
+            [
+                'nuovaTipologia.required' => 'Scrivi il nome della tipologia.',
+                'nuovaTipologia.unique' => 'Questa tipologia esiste già: sceglila dall\'elenco.',
+            ],
+        );
+
+        $tipologia = Tipologia::create(['nome' => $dati['nuovaTipologia'], 'attivo' => true]);
+
+        $this->tipologiaId = (string) $tipologia->id;
+        $this->nuovaTipologia = '';
+        $this->updatedTipologiaId();
+        $this->avvisa("Tipologia «{$tipologia->nome}» creata e selezionata.");
+    }
+
+    // ─── Pubblicazione ed eliminazione ──────────────────────────────────────
+
+    public function pubblica(): void
+    {
+        $mappa = $this->mappaAperta();
+
+        if (! $mappa) {
+            return;
+        }
+
+        if ($motivo = $mappa->motivoNonPubblicabile()) {
+            $this->avvisaErrore($motivo);
+
+            return;
+        }
+
+        $this->dispatch('pubblica-piantina', mappaId: $mappa->id)->to(Pubblicazione::class);
+    }
+
+    #[On('piantina-pubblicata')]
+    public function pubblicata(int $mappaId): void
+    {
+        $mappa = TerritorioMappa::with('territorio.zona')->find($mappaId);
+
+        if ($mappa) {
+            $this->dispatch('piantina-aggiornata', piantina: $this->datiPiantina($mappa));
+        }
+    }
+
+    public function elimina(): void
+    {
+        $mappa = $this->mappaAperta();
+
+        if (! $mappa) {
+            return;
+        }
+
+        $etichetta = $mappa->etichetta();
+        $id = $mappa->id;
+
+        if ($mappa->image_path) {
+            Storage::disk('public')->delete($mappa->image_path);
+        }
+        $mappa->delete();
+
+        $this->svuota();
+        $this->dispatch('piantina-rimossa', mappaId: $id);
+        $this->avvisa("{$etichetta} eliminata. Il territorio e il suo PDF restano com'erano.");
+    }
+
+    // ─── Dati per la mappa ──────────────────────────────────────────────────
+
+    /** Chiamata una volta dalla mappa all'avvio ($wire.datiMappa()). */
+    public function datiMappa(PiantineArea $area): array
+    {
+        return [
+            'area' => $area->area(),
+            'piantine' => TerritorioMappa::with('territorio.zona')->get()
+                ->filter(fn (TerritorioMappa $m) => $m->geometria() !== null)
+                ->map(fn (TerritorioMappa $m) => $this->datiPiantina($m))
+                ->values()
+                ->all(),
+            'selezionata' => $this->mappaId,
+        ];
+    }
+
+    private function datiPiantina(TerritorioMappa $mappa): array
+    {
+        return [
+            'mappaId' => $mappa->id,
+            'etichetta' => $mappa->etichetta(),
+            'collegata' => $mappa->collegata(),
+            'stato' => $mappa->stato(),
+            'statoEtichetta' => $mappa->statoEtichetta(),
+            'geometry' => $mappa->geometria(),
+        ];
+    }
+
+    /** Dopo ogni salvataggio automatico: ora in testata, mappa e indirizzo allineati. */
+    private function salvato(?TerritorioMappa $mappa, bool $seleziona = false): void
+    {
+        if (! $mappa) {
+            return;
+        }
+
+        $mappa = $mappa->fresh(['territorio.zona']);
+        $this->salvatoAlle = now()->format('H:i');
+
+        $this->dispatch('piantina-aggiornata', piantina: $this->datiPiantina($mappa));
+
+        if ($seleziona) {
+            $this->dispatch('piantina-selezionata', mappaId: $mappa->id, inquadra: false);
+        }
+
+        // La piantina aperta resta nell'indirizzo: ricaricando la pagina si
+        // torna su questa e non su un editor vuoto.
+        $this->dispatch('editor-indirizzo', url: route('piantine.editor', $mappa->id));
+    }
+
+    private function mappaAperta(): ?TerritorioMappa
+    {
+        return $this->mappaId ? TerritorioMappa::with('territorio.zona')->find($this->mappaId) : null;
+    }
+
+    private function territorioCollegato(): ?Territorio
+    {
+        if ($this->territorioScelto === '' || $this->territorioScelto === 'nuovo') {
+            return null;
+        }
+
+        $mappa = $this->mappaAperta();
+
+        return $mappa?->territorio;
+    }
+
+    public function render()
+    {
+        $mappa = $this->mappaAperta();
+
+        // Nella tendina: i territori attivi senza piantina, più quello già
+        // collegato anche se nel frattempo è stato disattivato o cestinato.
+        $occupati = TerritorioMappa::whereNotNull('territorio_id')
+            ->when($mappa, fn ($q) => $q->whereKeyNot($mappa->id))
+            ->pluck('territorio_id');
+
+        $territori = Territorio::attivi()
+            ->with(['zona:id,nome', 'tipologia:id,nome'])
+            ->whereNotIn('id', $occupati)
+            ->orderByRaw('LENGTH(numero), numero')
+            ->get(['id', 'numero', 'zona_id', 'tipologia_id', 'attivo', 'deleted_at']);
+
+        if ($mappa?->territorio && ! $territori->contains('id', $mappa->territorio_id)) {
+            $territori->prepend($mappa->territorio);
+        }
+
+        // Il campo di scelta con ricerca (<x-scelta>): due voci fisse in cima,
+        // poi i territori, che qui restano sceglibili anche se cestinati o
+        // disattivati (è il collegamento che già c'era).
+        $opzioniTerritori = [
+            ['valore' => '', 'etichetta' => '— nessun territorio —', 'speciale' => true],
+            ['valore' => 'nuovo', 'etichetta' => '+ Crea un territorio nuovo', 'speciale' => true],
+            ...$territori->map(function (Territorio $t) {
+                $opzione = $t->opzioneScelta(nota: $t->trashed() ? 'nel cestino' : (! $t->attivo ? 'disattivato' : null));
+                $opzione['etichetta'] = str_replace('N° ', 'Territorio ', $opzione['etichetta']);
+
+                return $opzione;
+            })->all(),
+        ];
+
+        return view('livewire.piantine.piantine-editor', [
+            'mappa' => $mappa,
+            'areaCaricata' => app(PiantineArea::class)->config()['kml_nome'] !== null,
+            'opzioniTerritori' => $opzioniTerritori,
+            'zone' => Zona::orderBy('nome')->get(['id', 'nome']),
+            'tipologie' => Tipologia::orderBy('nome')->get(['id', 'nome']),
+            'title' => $mappa ? $mappa->etichetta() . ' — Editor delle piantine' : 'Editor delle piantine',
+        ]);
+    }
+}

app/Livewire/Piantine/PiantineManager.php

@@ -0,0 +1,233 @@
+<?php
+
+namespace App\Livewire\Piantine;
+
+use App\Livewire\Concerns\Avvisa;
+use App\Models\TerritorioMappa;
+use App\Models\TerritorioPdfVersione;
+use App\Services\Piantine\PiantinaPdfService;
+use App\Services\Piantine\PiantineArea;
+use Illuminate\Support\Collection;
+use Illuminate\Support\Facades\Storage;
+use Livewire\Attributes\On;
+use Livewire\Attributes\Url;
+use Livewire\Component;
+use Livewire\WithFileUploads;
+use Livewire\WithPagination;
+
+/**
+ * Pagina di gestione delle piantine (solo amministratore).
+ *
+ * È il quadro d'insieme: a che punto è ogni piantina (bozza, pubblicata,
+ * con modifiche da pubblicare), l'area della città e lo storico dei PDF
+ * sostituiti. Il disegno e i dati del territorio si toccano nell'editor;
+ * da qui si apre, si pubblica (con la stessa finestra di anteprima
+ * dell'editor) e si elimina.
+ */
+class PiantineManager extends Component
+{
+    use Avvisa;
+    use WithFileUploads;
+    use WithPagination;
+
+    public const FILTRI = [
+        'tutte' => 'Tutte',
+        'bozze' => 'Bozze',
+        'da-pubblicare' => 'Da pubblicare',
+        'pubblicate' => 'Pubblicate',
+        'scollegate' => 'Scollegate',
+    ];
+
+    #[Url(as: 'q', except: '')]
+    public string $cerca = '';
+
+    #[Url(except: 'tutte')]
+    public string $filtro = 'tutte';
+
+    public $kmlFile = null;
+
+    public function updatedFiltro(): void
+    {
+        if (! array_key_exists($this->filtro, self::FILTRI)) {
+            $this->filtro = 'tutte';
+        }
+    }
+
+    // ─── Area città (KML) ───────────────────────────────────────────────────
+
+    public function caricaKml(PiantineArea $area): void
+    {
+        $this->validate(
+            ['kmlFile' => 'required|file|max:10240'],
+            [],
+            ['kmlFile' => 'file KML'],
+        );
+
+        $estensione = strtolower($this->kmlFile->getClientOriginalExtension());
+        if (! in_array($estensione, ['kml', 'xml'], true)) {
+            $this->addError('kmlFile', 'Il file deve essere un .kml (o .xml in formato KML).');
+
+            return;
+        }
+
+        try {
+            $quante = $area->salvaKml(
+                file_get_contents($this->kmlFile->getRealPath()),
+                $this->kmlFile->getClientOriginalName(),
+            );
+        } catch (\Throwable $e) {
+            $this->addError('kmlFile', $e->getMessage());
+
+            return;
+        }
+
+        $this->kmlFile = null;
+
+        activity()->causedBy(auth()->user())->log('piantine_kml_caricato');
+        $this->avvisa("Area della città aggiornata: {$quante} geometrie riconosciute nel KML.");
+    }
+
+    // ─── Piantine ───────────────────────────────────────────────────────────
+
+    public function pubblica(int $mappaId): void
+    {
+        $mappa = TerritorioMappa::with('territorio.zona')->find($mappaId);
+
+        if (! $mappa) {
+            $this->avvisaErrore('La piantina non esiste più.');
+
+            return;
+        }
+
+        if ($motivo = $mappa->motivoNonPubblicabile()) {
+            $this->avvisaErrore("{$mappa->etichetta()}: {$motivo}");
+
+            return;
+        }
+
+        $this->dispatch('pubblica-piantina', mappaId: $mappa->id)->to(Pubblicazione::class);
+    }
+
+    /** La finestra di pubblicazione ha finito: basta ridisegnare l'elenco. */
+    #[On('piantina-pubblicata')]
+    public function pubblicata(): void {}
+
+    public function elimina(int $mappaId): void
+    {
+        $mappa = TerritorioMappa::with('territorio')->find($mappaId);
+
+        if (! $mappa) {
+            return;
+        }
+
+        $etichetta = $mappa->etichetta();
+
+        if ($mappa->image_path) {
+            Storage::disk('public')->delete($mappa->image_path);
+        }
+        $mappa->delete();
+
+        $this->avvisa("{$etichetta} eliminata. Il territorio e il suo PDF restano com'erano.");
+    }
+
+    // ─── Storico versioni ───────────────────────────────────────────────────
+
+    public function ripristinaVersione(int $versioneId, PiantinaPdfService $pdfService): void
+    {
+        $versione = TerritorioPdfVersione::with('territorio')->find($versioneId);
+
+        if (! $versione) {
+            return;
+        }
+
+        $numero = $versione->territorio?->numero ?? '?';
+
+        try {
+            $pdfService->ripristina($versione);
+        } catch (\Throwable $e) {
+            $this->avvisaErrore($e->getMessage());
+
+            return;
+        }
+
+        $this->avvisa("Versione precedente ripristinata per il territorio {$numero}. Il PDF che c'era è nello storico.");
+    }
+
+    public function eliminaVersione(int $versioneId): void
+    {
+        $versione = TerritorioPdfVersione::find($versioneId);
+
+        if (! $versione) {
+            return;
+        }
+
+        Storage::disk('public')->delete($versione->pdf_path);
+        $versione->delete();
+
+        $this->avvisa('Versione eliminata definitivamente.');
+    }
+
+    // ─── Dati per la vista ──────────────────────────────────────────────────
+
+    /**
+     * Tutte le piantine con il loro stato, in memoria: sono qualche centinaio
+     * al massimo, e lo stato dipende dall'impronta, che si calcola in PHP.
+     *
+     * @return Collection<int, TerritorioMappa>
+     */
+    private function piantine(): Collection
+    {
+        return TerritorioMappa::with('territorio.zona')
+            ->get()
+            ->sortBy(fn (TerritorioMappa $m) => [
+                $m->territorio_id === null ? 1 : 0,
+                strlen((string) $m->territorio?->numero),
+                (string) $m->territorio?->numero,
+                mb_strtolower((string) $m->nome),
+            ])
+            ->values();
+    }
+
+    private function corrisponde(TerritorioMappa $mappa, string $filtro): bool
+    {
+        return match ($filtro) {
+            'bozze' => $mappa->stato() === TerritorioMappa::STATO_BOZZA,
+            'da-pubblicare' => $mappa->stato() === TerritorioMappa::STATO_MODIFICATA,
+            'pubblicate' => $mappa->stato() === TerritorioMappa::STATO_PUBBLICATA,
+            'scollegate' => ! $mappa->collegata(),
+            default => true,
+        };
+    }
+
+    public function render(PiantineArea $area)
+    {
+        $piantine = $this->piantine();
+
+        $conteggi = collect(self::FILTRI)
+            ->map(fn ($etichetta, $filtro) => $piantine->filter(fn ($m) => $this->corrisponde($m, $filtro))->count());
+
+        $cerca = mb_strtolower(trim($this->cerca));
+
+        $elenco = $piantine
+            ->filter(fn ($m) => $this->corrisponde($m, $this->filtro))
+            ->filter(fn (TerritorioMappa $m) => $cerca === '' || str_contains(mb_strtolower(implode(' ', [
+                $m->etichetta(),
+                $m->territorio?->numero,
+                $m->nome,
+                $m->territorio?->zona?->nome,
+            ])), $cerca))
+            ->values();
+
+        return view('livewire.piantine.piantine-manager', [
+            'config' => $area->config(),
+            'elenco' => $elenco,
+            'totale' => $piantine->count(),
+            'conteggi' => $conteggi,
+            'versioni' => TerritorioPdfVersione::with('territorio')
+                ->orderByDesc('sostituito_il')
+                ->orderByDesc('id')
+                ->paginate(15, pageName: 'versioni'),
+            'title' => 'Piantine dei territori',
+        ]);
+    }
+}

app/Livewire/Piantine/Pubblicazione.php

@@ -0,0 +1,124 @@
+<?php
+
+namespace App\Livewire\Piantine;
+
+use App\Livewire\Concerns\Avvisa;
+use App\Models\TerritorioMappa;
+use App\Services\Piantine\PubblicazionePiantina;
+use Livewire\Attributes\Locked;
+use Livewire\Attributes\On;
+use Livewire\Component;
+
+/**
+ * La finestra di pubblicazione, uguale nell'editor e nella gestione.
+ *
+ * Si apre con l'evento "pubblica-piantina", prepara l'anteprima in coda
+ * (controllando a intervalli quando è pronta), la mostra, e solo su
+ * "Conferma" sostituisce il PDF del territorio. Chiuderla butta l'anteprima.
+ */
+class Pubblicazione extends Component
+{
+    use Avvisa;
+
+    #[Locked]
+    public ?int $mappaId = null;
+
+    #[Locked]
+    public ?string $token = null;
+
+    public string $fase = '';
+
+    public string $messaggio = '';
+
+    public string $etichetta = '';
+
+    #[On('pubblica-piantina')]
+    public function apri(int $mappaId, PubblicazionePiantina $pubblicazione): void
+    {
+        $this->chiudi($pubblicazione);
+
+        $mappa = TerritorioMappa::with('territorio.zona')->find($mappaId);
+        if (! $mappa) {
+            $this->avvisaErrore('La piantina non esiste più.');
+
+            return;
+        }
+
+        $this->mappaId = $mappa->id;
+        $this->etichetta = $mappa->etichetta();
+
+        try {
+            $this->token = $pubblicazione->avvia($mappa);
+        } catch (\RuntimeException $e) {
+            $this->fase = PubblicazionePiantina::ERRORE;
+            $this->messaggio = $e->getMessage();
+
+            return;
+        }
+
+        $this->aggiorna($pubblicazione);
+    }
+
+    /** Chiamata a intervalli finché l'anteprima è in preparazione. */
+    public function aggiorna(PubblicazionePiantina $pubblicazione): void
+    {
+        if (! $this->token) {
+            return;
+        }
+
+        $stato = $pubblicazione->stato($this->token);
+
+        if (! $stato) {
+            $this->fase = PubblicazionePiantina::ERRORE;
+            $this->messaggio = 'L\'anteprima è scaduta: generala di nuovo.';
+
+            return;
+        }
+
+        $this->fase = $stato['stato'];
+        $this->messaggio = $stato['messaggio'] ?? '';
+    }
+
+    public function conferma(PubblicazionePiantina $pubblicazione): void
+    {
+        if (! $this->token) {
+            return;
+        }
+
+        try {
+            $mappa = $pubblicazione->conferma($this->token);
+        } catch (\RuntimeException $e) {
+            $this->fase = PubblicazionePiantina::ERRORE;
+            $this->messaggio = $e->getMessage();
+
+            return;
+        }
+
+        $this->reset(['mappaId', 'token', 'fase', 'messaggio', 'etichetta']);
+
+        $this->avvisa("{$mappa->etichetta()} pubblicata: il PDF del territorio è stato sostituito, il precedente è nello storico.");
+        $this->dispatch('piantina-pubblicata', mappaId: $mappa->id);
+    }
+
+    /** Riprova dopo un errore, con lo stato attuale della piantina. */
+    public function riprova(PubblicazionePiantina $pubblicazione): void
+    {
+        if ($this->mappaId) {
+            $this->apri($this->mappaId, $pubblicazione);
+        }
+    }
+
+    public function chiudi(PubblicazionePiantina $pubblicazione): void
+    {
+        if ($this->token) {
+            $pubblicazione->annulla($this->token);
+        }
+
+        $this->reset(['mappaId', 'token', 'fase', 'messaggio', 'etichetta']);
+    }
+
+    public function render()
+    {
+        return view('livewire.piantine.pubblicazione');
+    }
+}

app/Livewire/Privacy.php

@@ -2,18 +2,89 @@
 
 namespace App\Livewire;
 
-use Livewire\Component;
+use App\Models\Assegnazione;
+use App\Models\Proclamatore;
+use App\Models\Richiesta;
 use App\Models\Setting;
+use App\Models\User;
+use App\Services\ConfigurazionePosta;
+use Livewire\Component;
+use Spatie\Activitylog\Models\Activity;
+use Spatie\Permission\Models\Role;
 
+/**
+ * Informativa privacy (solo amministratore).
+ *
+ * Tutto ciò che può cambiare si legge qui, al momento: impostazioni
+ * (congregazione, conservazione del log, scadenza dei link, download del
+ * PDF, server di posta), configurazione (indirizzo, cifratura, durata della
+ * sessione), ruoli con i loro permessi reali e quanti dati sono conservati.
+ * Il testo resta nella vista; i numeri non vanno mai scritti a mano.
+ */
 class Privacy extends Component
 {
+    /** Data dell'ultima revisione del testo dell'informativa. */
+    public const REVISIONE = '21 ottobre 2026';
+
+    /** I permessi spiegati a chi legge l'informativa. */
+    public const PERMESSI = [
+        'settings.manage' => 'impostazioni, utenti, backup e import',
+        'proclamatori.manage' => 'anagrafica dei proclamatori',
+        'gruppo.gestisci' => 'solo il proprio gruppo di servizio: i territori del pacchetto e i membri del gruppo',
+        'territori.manage' => 'gestione dei territori e delle piantine',
+        'campagne.manage' => 'campagne',
+        'registro.view' => 'consultazione del registro delle assegnazioni',
+        'registro.export' => 'esportazione del registro',
+        'territori.assign' => 'assegnazione dei territori',
+        'territori.return' => 'rientro dei territori',
+        'richieste.gestisci' => 'richieste arrivate dal modulo pubblico (nuovo territorio o riconsegna)',
+        'audit.view' => 'consultazione del registro delle attività',
+        'audit.export' => 'esportazione del registro delle attività',
+    ];
+
     public function render()
     {
-        $settings = Setting::instance();
+        $impostazioni = Setting::instance();
+        $posta = app(ConfigurazionePosta::class);
+
+        $hostPosta = $posta->configurataNellApp()
+            ? (string) $impostazioni->mail_host
+            : (string) config('mail.mailers.smtp.host');
+
+        $indirizzo = (string) config('app.url');
 
         return view('livewire.privacy', [
-            'congregazione' => $settings->congregazione_nome ?? 'Congregazione',
-            'auditRetention' => $settings->audit_retention_days ?? 365,
+            'revisione' => self::REVISIONE,
+            'congregazione' => $impostazioni->congregazione_nome ?: 'Congregazione',
+            'indirizzo' => $indirizzo,
+            'https' => str_starts_with($indirizzo, 'https://'),
+            'cifratura' => (string) config('app.cipher'),
+            'durataSessione' => (int) config('session.lifetime'),
+            'auditRetention' => (int) ($impostazioni->audit_retention_days ?: 365),
+            'scadenzaLink' => max(1, (int) ($impostazioni->giorni_per_smarrito ?: 120)),
+            'downloadPdf' => (bool) $impostazioni->pdf_viewer_show_download,
+            'postaAttiva' => $posta->funzionante(),
+            'hostPosta' => $hostPosta !== '' ? $hostPosta : null,
+            'ruoli' => Role::with('permissions')->orderBy('name')->get()->map(fn (Role $r) => [
+                'nome' => $r->name,
+                'permessi' => $r->permissions->pluck('name')
+                    ->map(fn ($p) => self::PERMESSI[$p] ?? $p)
+                    ->all(),
+            ]),
+            // Quanti dati sono conservati adesso: solo conteggi, contati in
+            // SQL, senza decifrare né mostrare nomi.
+            'conteggi' => [
+                'proclamatori' => Proclamatore::count(),
+                'proclamatoriAttivi' => Proclamatore::where('attivo', true)->count(),
+                'anonimizzati' => Proclamatore::onlyTrashed()->count(),
+                'utenti' => User::count(),
+                'assegnazioni' => Assegnazione::count(),
+                'assegnazioniAperte' => Assegnazione::aperte()->count(),
+                'richieste' => Richiesta::count(),
+                'richiesteAperte' => Richiesta::aperte()->count(),
+                'attivita' => Activity::count(),
+                'attivitaDal' => Activity::min('created_at'),
+            ],
         ]);
     }
 }

app/Livewire/Proclamatori/ProclamatoreCestino.php

@@ -2,37 +2,43 @@
 
 namespace App\Livewire\Proclamatori;
 
+use App\Livewire\Concerns\Avvisa;
 use Livewire\Component;
 use Livewire\WithPagination;
 use App\Models\Proclamatore;
 
 class ProclamatoreCestino extends Component
 {
+    use Avvisa;
     use WithPagination;
 
     public function restore(int $id)
     {
+        $this->authorize('settings.manage');
+
         $proclamatore = Proclamatore::onlyTrashed()->findOrFail($id);
         $proclamatore->restore();
         activity()->causedBy(auth()->user())
             ->performedOn($proclamatore)
             ->log('restored');
-        session()->flash('success', "Proclamatore ripristinato.");
+        $this->avvisa("Proclamatore ripristinato.");
     }
 
     public function forceDelete(int $id)
     {
+        $this->authorize('settings.manage');
+
         $proclamatore = Proclamatore::onlyTrashed()->findOrFail($id);
 
         if ($proclamatore->assegnazioni()->exists()) {
-            session()->flash('error', 'Impossibile eliminare definitivamente: il proclamatore ha assegnazioni nello storico.');
+            $this->avvisaErrore('Impossibile eliminare definitivamente: il proclamatore ha assegnazioni nello storico.');
             return;
         }
 
         activity()->causedBy(auth()->user())
             ->log('force_deleted_proclamatore');
         $proclamatore->forceDelete();
-        session()->flash('success', 'Proclamatore eliminato definitivamente.');
+        $this->avvisa('Proclamatore eliminato definitivamente.');
     }
 
     public function render()

app/Livewire/Proclamatori/ProclamatoreCreate.php

@@ -2,11 +2,14 @@
 
 namespace App\Livewire\Proclamatori;
 
+use App\Livewire\Concerns\RicordaRitorno;
 use Livewire\Component;
 use App\Models\Proclamatore;
 
 class ProclamatoreCreate extends Component
 {
+    use RicordaRitorno;
+
     public string $nome = '';
     public string $cognome = '';
     public bool $attivo = true;
@@ -22,6 +25,8 @@ class ProclamatoreCreate extends Component
 
     public function save()
     {
+        $this->authorize('settings.manage');
+
         $this->validate();
 
         $proclamatore = Proclamatore::create([
@@ -35,7 +40,7 @@ class ProclamatoreCreate extends Component
             ->log('created');
 
         session()->flash('success', "Proclamatore {$proclamatore->nome_completo} creato.");
-        return $this->redirect(route('proclamatori.index'), navigate: true);
+        return $this->redirect($this->destinazione(route('proclamatori.index')), navigate: true);
     }
 
     public function render()

app/Livewire/Proclamatori/ProclamatoreEdit.php

@@ -2,11 +2,14 @@
 
 namespace App\Livewire\Proclamatori;
 
+use App\Livewire\Concerns\RicordaRitorno;
 use Livewire\Component;
 use App\Models\Proclamatore;
 
 class ProclamatoreEdit extends Component
 {
+    use RicordaRitorno;
+
     public Proclamatore $proclamatore;
     public string $nome = '';
     public string $cognome = '';
@@ -31,16 +34,22 @@ class ProclamatoreEdit extends Component
 
     public function save()
     {
+        $this->authorize('settings.manage');
+
         $this->validate();
 
+        // Un sorvegliante reso non attivo scioglie il gruppo (Proclamatore::booted).
+        $gruppo = ! $this->attivo ? $this->proclamatore->gruppoSorvegliato() : null;
+
         $this->proclamatore->update([
             'nome' => $this->nome,
             'cognome' => $this->cognome,
             'attivo' => $this->attivo,
         ]);
 
-        session()->flash('success', "Proclamatore {$this->proclamatore->nome_completo} aggiornato.");
-        return $this->redirect(route('proclamatori.index'), navigate: true);
+        $avviso = "Proclamatore {$this->proclamatore->nome_completo} aggiornato." . ($gruppo ? ' ' . ProclamatoreIndex::gruppoSciolto($gruppo) : '');
+        session()->flash('success', $avviso);
+        return $this->redirect($this->destinazione(route('proclamatori.index')), navigate: true);
     }
 
     public function render()
@@ -48,6 +57,7 @@ class ProclamatoreEdit extends Component
         return view('livewire.proclamatori.proclamatore-form', [
             'titolo' => "Modifica {$this->proclamatore->nome_completo}",
             'btnLabel' => 'Salva Modifiche',
+            'gruppoSorvegliato' => $this->proclamatore->gruppoSorvegliato(),
         ]);
     }
 }

app/Livewire/Proclamatori/ProclamatoreIndex.php

@@ -2,17 +2,26 @@
 
 namespace App\Livewire\Proclamatori;
 
+use App\Livewire\Concerns\Avvisa;
+use Livewire\Attributes\Url;
 use Livewire\Component;
 use Livewire\WithPagination;
+use App\Models\GruppoServizio;
 use App\Models\Proclamatore;
 
 class ProclamatoreIndex extends Component
 {
+    use Avvisa;
     use WithPagination;
 
+    // Ricerca, filtro e ordinamento nell'indirizzo: si ritrovano tornando.
+    #[Url(except: '')]
     public string $search = '';
+    #[Url(except: '')]
     public string $filtroStato = '';
+    #[Url(except: 'cognome')]
     public string $sortField = 'cognome';
+    #[Url(except: 'asc')]
     public string $sortDirection = 'asc';
 
     protected $queryString = [
@@ -42,28 +51,54 @@ class ProclamatoreIndex extends Component
 
     public function toggleActive(int $id)
     {
+        // La lista è in sola lettura per i non-admin: creare/modificare/
+        // eliminare proclamatori è riservato all'amministratore. Il check sta
+        // nel metodo perché la rotta index resta accessibile con
+        // proclamatori.manage.
+        $this->authorize('settings.manage');
+
         $proclamatore = Proclamatore::findOrFail($id);
+        $gruppo = $proclamatore->attivo ? $proclamatore->gruppoSorvegliato() : null;
+        // Un sorvegliante reso non attivo scioglie il gruppo (Proclamatore::booted).
         $proclamatore->update(['attivo' => !$proclamatore->attivo]);
+
+        if ($gruppo) {
+            $this->avvisa("{$proclamatore->nome_completo} non è più attivo. " . self::gruppoSciolto($gruppo));
+        }
     }
 
     public function deleteProclamatore(int $id)
     {
+        $this->authorize('settings.manage');
+
         $proclamatore = Proclamatore::findOrFail($id);
 
         if ($proclamatore->assegnazioni()->aperte()->exists()) {
-            session()->flash('error', "Il proclamatore {$proclamatore->nome_completo} ha assegnazioni aperte. Rientra prima i territori.");
+            $this->avvisaErrore("Il proclamatore {$proclamatore->nome_completo} ha assegnazioni aperte. Rientra prima i territori.");
             return;
         }
 
+        // Nel cestino lascia il gruppo; se ne era il sorvegliante, il gruppo
+        // si scioglie (Proclamatore::booted).
+        $gruppo = $proclamatore->gruppoSorvegliato();
         $proclamatore->delete();
-        session()->flash('success', "Proclamatore {$proclamatore->nome_completo} spostato nel cestino.");
+        $this->avvisa("Proclamatore {$proclamatore->nome_completo} spostato nel cestino." . ($gruppo ? ' ' . self::gruppoSciolto($gruppo) : ''));
     }
 
     public function anonimizza(int $id)
     {
+        $this->authorize('settings.manage');
+
         $proclamatore = Proclamatore::findOrFail($id);
+        $gruppo = $proclamatore->gruppoSorvegliato();
         $proclamatore->anonimizza();
-        session()->flash('success', "Dati personali del proclamatore anonimizzati (GDPR).");
+        $this->avvisa("Dati personali del proclamatore anonimizzati (GDPR)." . ($gruppo ? ' ' . self::gruppoSciolto($gruppo) : ''));
+    }
+
+    /** L'avviso quando un sorvegliante esce di scena: anche per ProclamatoreEdit. */
+    public static function gruppoSciolto(GruppoServizio $gruppo): string
+    {
+        return "Era il sorvegliante del gruppo {$gruppo->nome}: il gruppo è stato sciolto, i territori non ancora dati sono tornati in reparto e la sua utenza è stata eliminata.";
     }
 
     public function render()
@@ -71,7 +106,7 @@ class ProclamatoreIndex extends Component
         // withCount rather than letting the view call
         // ->assegnazioni()->aperte()->count() per row, which issued one
         // COUNT(*) per displayed proclamatore on every render.
-        $query = Proclamatore::query()->withCount([
+        $query = Proclamatore::query()->with('gruppo')->withCount([
             'assegnazioni as assegnazioni_aperte_count' => fn ($q) => $q->whereNull('returned_at'),
         ]);
 
@@ -89,6 +124,8 @@ class ProclamatoreIndex extends Component
                 $filtered = $filtered->where('attivo', true);
             } elseif ($this->filtroStato === 'inattivo') {
                 $filtered = $filtered->where('attivo', false);
+            } elseif ($this->filtroStato === 'gruppo') {
+                $filtered = $filtered->whereNotNull('gruppo_servizio_id');
             }
 
             // Sort in-memory
@@ -113,6 +150,8 @@ class ProclamatoreIndex extends Component
                 $query->where('attivo', true);
             } elseif ($this->filtroStato === 'inattivo') {
                 $query->where('attivo', false);
+            } elseif ($this->filtroStato === 'gruppo') {
+                $query->whereNotNull('gruppo_servizio_id');
             }
 
             // cognome/nome encrypted, so sort in-memory
@@ -135,6 +174,8 @@ class ProclamatoreIndex extends Component
 
         return view('livewire.proclamatori.proclamatore-index', [
             'proclamatori' => $proclamatori,
+            // Per avvisare, prima di disattivare o cestinare, che il gruppo si scioglie.
+            'gruppiSorvegliati' => GruppoServizio::pluck('nome', 'sorvegliante_id'),
         ]);
     }
 }

app/Livewire/Proclamatori/ProclamatoreShow.php

@@ -2,12 +2,16 @@
 
 namespace App\Livewire\Proclamatori;
 
+use App\Livewire\Concerns\RicordaRitorno;
 use Livewire\Component;
 use App\Models\Proclamatore;
 use App\Models\Assegnazione;
+use Spatie\Activitylog\Models\Activity;
 
 class ProclamatoreShow extends Component
 {
+    use RicordaRitorno;
+
     public Proclamatore $proclamatore;
 
     public function mount(Proclamatore $proclamatore)
@@ -20,8 +24,11 @@ class ProclamatoreShow extends Component
         $assegnazioni = Assegnazione::where('proclamatore_id', $this->proclamatore->id)
             ->with(['territorio', 'annoTeocratico', 'campagna'])
             ->orderByDesc('assigned_at')
+            ->orderByDesc('id')
             ->get()
-            ->groupBy(fn($a) => $a->annoTeocratico->label);
+            ->groupBy(fn($a) => $a->annoTeocratico->label)
+            // Dal più recente: gli anni ("2026-2027") si ordinano come testo.
+            ->sortKeysDesc();
 
         $stats = [
             'totale_assegnazioni' => Assegnazione::where('proclamatore_id', $this->proclamatore->id)->count(),
@@ -34,9 +41,21 @@ class ProclamatoreShow extends Component
             ),
         ];
 
+        // Gruppo di servizio: sorvegliante (con i dettagli del gruppo e della
+        // sua utenza) o membro. I gruppi sciolti non esistono più.
+        $gruppoSorvegliato = $this->proclamatore->gruppoSorvegliato();
+        $utenza = $gruppoSorvegliato ? $this->proclamatore->utente : null;
+
         return view('livewire.proclamatori.proclamatore-show', [
             'assegnazioniPerAnno' => $assegnazioni,
             'stats' => $stats,
+            'gruppoSorvegliato' => $gruppoSorvegliato,
+            'riepilogoGruppo' => $gruppoSorvegliato?->riepilogo(),
+            'gruppoMembro' => $gruppoSorvegliato ? null : $this->proclamatore->gruppo()->with('sorvegliante')->first(),
+            'utenza' => $utenza,
+            'ultimoAccesso' => $utenza
+                ? Activity::whereMorphedTo('causer', $utenza)->where('description', 'login')->max('created_at')
+                : null,
         ]);
     }
 }

app/Livewire/Profile.php

@@ -0,0 +1,102 @@
+<?php
+
+namespace App\Livewire;
+
+use App\Livewire\Concerns\Avvisa;
+use Illuminate\Validation\Rule;
+use Livewire\Component;
+
+class Profile extends Component
+{
+    use Avvisa;
+    public string $name = '';
+    public string $email = '';
+
+    public string $current_password = '';
+    public string $password = '';
+    public string $password_confirmation = '';
+
+    public function mount(): void
+    {
+        $user = auth()->user();
+        $this->name = $user->name;
+        $this->email = $user->email;
+    }
+
+    public function updateProfile()
+    {
+        $user = auth()->user();
+
+        // Il sorvegliante di gruppo entra con l'email fittizia creata col
+        // gruppo (GruppiServizio::emailFittizia): dal profilo non la cambia.
+        $emailFissa = $user->isSorvegliante();
+
+        $validated = $this->validate([
+            'name' => ['required', 'string', 'max:255'],
+        ] + ($emailFissa ? [] : [
+            'email' => ['required', 'email', 'max:255', Rule::unique('users', 'email')->ignore($user->id)],
+        ]));
+
+        $user->fill(['name' => $validated['name']] + ($emailFissa ? [] : ['email' => $validated['email']]));
+        $emailCambiata = $user->isDirty('email');
+        $user->save();
+
+        // L'indirizzo nuovo va confermato (User::booted lo segna da
+        // confermare): finché non apre il link, l'account resta bloccato.
+        // Il sorvegliante di gruppo non conferma l'email (User::hasVerifiedEmail).
+        if ($emailCambiata && ! $user->isSorvegliante()) {
+            $user->inviaConfermaEmail()
+                ? session()->flash('success', "Profilo aggiornato. Conferma il nuovo indirizzo: ti abbiamo mandato un'email a {$user->email}.")
+                : session()->flash('error', 'Profilo aggiornato, ma l\'email di conferma non è partita: richiedila qui sotto.');
+
+            return $this->redirect(route('verification.notice'), navigate: false);
+        }
+
+        session()->flash('profile_success', 'Profilo aggiornato con successo.');
+
+        // Ricarica la pagina così header e card mostrano subito i nuovi dati
+        // (l'header vive nel layout, fuori dal componente).
+        return $this->redirect(route('profile'), navigate: true);
+    }
+
+    public function updatePassword(): void
+    {
+        // `current_password` verifica che la password attuale digitata combaci
+        // con quella dell'utente loggato prima di consentire il cambio.
+        $this->validate([
+            'current_password' => ['required', 'current_password'],
+            'password' => ['required', 'string', 'min:8', 'confirmed'],
+        ]);
+
+        // Il cast `hashed` sul modello User cifra il valore in fase di salvataggio.
+        //
+        // Si spegne anche `password_change_required`: oggi chi ha quel flag
+        // viene dirottato dal middleware e questa pagina non la raggiunge
+        // nemmeno, ma la condizione che il flag esprime — "questa password non
+        // e' piu' un segreto" — la soddisfa qualunque cambio, non solo quello
+        // fatto dalla schermata obbligatoria. Lasciarlo acceso qui
+        // significherebbe che un domani, allentando il middleware, l'utente
+        // resterebbe bloccato dopo aver gia' fatto quello che gli si chiedeva.
+        auth()->user()->update([
+            'password' => $this->password,
+            'password_change_required' => false,
+            'password_temporanea' => false,
+        ]);
+
+        $this->reset(['current_password', 'password', 'password_confirmation']);
+
+        $this->avvisa('Password aggiornata con successo.');
+    }
+
+    public function render()
+    {
+        // Il sorvegliante vede qui i dettagli del suo gruppo di servizio.
+        $gruppo = auth()->user()->gruppoSorvegliato();
+
+        return view('livewire.profile', [
+            'user' => auth()->user(),
+            'gruppo' => $gruppo,
+            'riepilogoGruppo' => $gruppo?->riepilogo(),
+        ]);
+    }
+}

app/Livewire/Registro.php

@@ -2,6 +2,7 @@
 
 namespace App\Livewire;
 
+use Livewire\Attributes\Url;
 use Livewire\Component;
 use Livewire\WithPagination;
 use App\Models\Assegnazione;
@@ -11,17 +12,28 @@ use App\Models\Proclamatore;
 use App\Models\Territorio;
 use App\Models\Zona;
 use App\Models\Tipologia;
+use App\Services\Registro\ModuloS13;
+use Carbon\Carbon;
+use Illuminate\Support\Facades\DB;
 
 class Registro extends Component
 {
     use WithPagination;
 
+    // Ricerca, filtri e ordinamento nell'indirizzo: si ritrovano tornando.
+    #[Url(except: '')]
     public string $search = '';
+    #[Url(except: '')]
     public string $filtroAnno = '';
+    #[Url(except: '')]
     public string $filtroZona = '';
+    #[Url(except: '')]
     public string $filtroTipologia = '';
+    #[Url(except: '')]
     public string $filtroStato = ''; // aperte, chiuse
+    #[Url(except: 'territorio_numero')]
     public string $sortField = 'territorio_numero';
+    #[Url(except: 'asc')]
     public string $sortDirection = 'asc';
 
     // ─── Modal create/edit ──────────────────────────────────────
@@ -30,7 +42,6 @@ class Registro extends Component
 
     public string $form_territorio_id = '';
     public string $form_proclamatore_id = '';
-    public string $form_anno_id = '';
     public string $form_assigned_at = '';
     public string $form_returned_at = '';
     public bool $form_counted_in_campaign = false;
@@ -41,6 +52,10 @@ class Registro extends Component
     public bool $showDeleteConfirm = false;
     public ?int $deleteId = null;
 
+    // ─── Modal modulo S-13 ──────────────────────────────────────
+    public bool $showS13Modal = false;
+    public string $s13Anno = '';
+
     protected $queryString = [
         'search' => ['except' => ''],
         'filtroAnno' => ['except' => ''],
@@ -90,7 +105,6 @@ class Registro extends Component
         $this->editingId = null;
         $this->form_territorio_id = '';
         $this->form_proclamatore_id = '';
-        $this->form_anno_id = '';
         $this->form_assigned_at = now()->format('Y-m-d');
         $this->form_returned_at = '';
         $this->form_counted_in_campaign = false;
@@ -107,7 +121,6 @@ class Registro extends Component
         $this->editingId = $id;
         $this->form_territorio_id = (string) $a->territorio_id;
         $this->form_proclamatore_id = (string) $a->proclamatore_id;
-        $this->form_anno_id = (string) $a->anno_teocratico_id;
         $this->form_assigned_at = $a->assigned_at?->format('Y-m-d') ?? '';
         $this->form_returned_at = $a->returned_at?->format('Y-m-d') ?? '';
         $this->form_counted_in_campaign = (bool) $a->counted_in_campaign;
@@ -123,28 +136,69 @@ class Registro extends Component
         $this->validate([
             'form_territorio_id'     => 'required|exists:territori,id',
             'form_proclamatore_id'   => 'required|exists:proclamatori,id',
-            'form_anno_id'           => 'required|exists:anni_teocratici,id',
-            'form_assigned_at'       => 'required|date',
-            'form_returned_at'       => 'nullable|date|after_or_equal:form_assigned_at',
+            'form_assigned_at'       => 'required|date|before_or_equal:today',
+            'form_returned_at'       => 'nullable|date|after_or_equal:form_assigned_at|before_or_equal:today',
             'form_campaign_id'       => 'nullable|exists:campagne,id',
+        ], [
+            'form_assigned_at.before_or_equal' => 'La data di assegnazione non può essere futura.',
+            'form_returned_at.before_or_equal' => 'La data di rientro non può essere futura.',
+            'form_returned_at.after_or_equal'  => 'Il rientro non può precedere l\'assegnazione.',
         ]);
 
+        $uscita = Carbon::parse($this->form_assigned_at);
+        $rientro = $this->form_returned_at ? Carbon::parse($this->form_returned_at) : null;
+
+        // L'anno di servizio non si sceglie: è quello della data di uscita.
+        // Scelto a mano poteva restare incoerente con la data, e l'assegnazione
+        // finiva contata nell'anno sbagliato da Home, filtri e modulo S-13.
         $data = [
             'territorio_id'       => $this->form_territorio_id,
             'proclamatore_id'     => $this->form_proclamatore_id,
-            'anno_teocratico_id'  => $this->form_anno_id,
-            'assigned_at'         => $this->form_assigned_at,
-            'returned_at'         => $this->form_returned_at ?: null,
-            'counted_in_campaign' => $this->form_counted_in_campaign,
+            'anno_teocratico_id'  => AnnoTeocratico::perData($uscita)->id,
+            'assigned_at'         => $uscita,
+            'returned_at'         => $rientro,
+            // "Contata nella campagna" senza campagna non ha significato.
+            'counted_in_campaign' => $this->form_counted_in_campaign && $this->form_campaign_id !== '',
             'campaign_id'         => $this->form_campaign_id ?: null,
             'note'                => $this->form_note ?: null,
         ];
 
-        if ($this->editingId) {
-            Assegnazione::findOrFail($this->editingId)->update($data);
-        } else {
-            $data['created_by'] = auth()->id();
-            Assegnazione::create($data);
+        $assegnazione = null;
+        $prima = [false, null];
+
+        $conflitto = DB::transaction(function () use ($data, $uscita, $rientro, &$assegnazione, &$prima) {
+            Territorio::whereKey($data['territorio_id'])->lockForUpdate()->first();
+
+            $conflitto = Assegnazione::sovrappostaA((int) $data['territorio_id'], $uscita, $rientro, $this->editingId);
+            if ($conflitto) {
+                return $conflitto;
+            }
+
+            if ($this->editingId) {
+                $assegnazione = Assegnazione::findOrFail($this->editingId);
+                $prima = [(bool) $assegnazione->counted_in_campaign, $assegnazione->campaign_id ? (int) $assegnazione->campaign_id : null];
+                $assegnazione->update($data);
+            } else {
+                $assegnazione = Assegnazione::create($data + ['created_by' => auth()->id()]);
+            }
+
+            return null;
+        });
+
+        if ($conflitto) {
+            $this->addError('form_assigned_at', "Il periodo si sovrappone all'assegnazione {$conflitto->descrizionePeriodo()}.");
+
+            return;
+        }
+
+        // Log the campaign choice when the admin sets or changes it here.
+        $dopo = [(bool) $assegnazione->counted_in_campaign, $assegnazione->campaign_id ? (int) $assegnazione->campaign_id : null];
+        if ($dopo !== $prima && ($dopo[0] || $prima[0])) {
+            $assegnazione->logCampagnaPercorso(
+                $assegnazione->campagna ?? ($prima[1] ? Campagna::find($prima[1]) : null),
+                $dopo[0],
+                'Registro'
+            );
         }
 
         $this->showModal = false;
@@ -167,6 +221,60 @@ class Registro extends Component
         $this->showDeleteConfirm = false;
     }
 
+    // ─── Modulo S-13 ────────────────────────────────────────────
+
+    /**
+     * Chiede quale anno di servizio stampare. L'anno del filtro è solo la
+     * proposta iniziale: il modulo finisce in archivio e viene firmato, quindi
+     * la scelta va confermata invece di essere ereditata da uno stato della
+     * pagina che l'utente può non avere presente.
+     */
+    public function openS13(): void
+    {
+        abort_if(!auth()->user()->can('settings.manage'), 403);
+
+        $this->s13Anno = $this->filtroAnno !== ''
+            ? $this->filtroAnno
+            : (string) AnnoTeocratico::corrente()->id;
+
+        $this->resetValidation();
+        $this->showS13Modal = true;
+    }
+
+    /**
+     * Modulo ufficiale S-13-I compilato per l'anno di servizio scelto nella
+     * modale; le regole di compilazione stanno in ModuloS13.
+     *
+     * Solo amministratore, come il resto del CRUD di questa pagina: il modulo
+     * espone in un unico file l'anagrafica completa di chi ha avuto quale
+     * territorio, dati personali che il ruolo assegnatario non deve poter
+     * esportare in blocco.
+     */
+    public function downloadS13(ModuloS13 $modulo)
+    {
+        abort_if(!auth()->user()->can('settings.manage'), 403);
+
+        $this->validate(
+            ['s13Anno' => 'required|exists:anni_teocratici,id'],
+            [
+                's13Anno.required' => "Seleziona l'anno di servizio da stampare.",
+                's13Anno.exists'   => "L'anno di servizio selezionato non esiste.",
+            ]
+        );
+
+        $anno = AnnoTeocratico::findOrFail($this->s13Anno);
+
+        $this->showS13Modal = false;
+
+        $pdf = $modulo->genera($anno);
+
+        return response()->streamDownload(
+            fn () => print($pdf),
+            'S-13-registro-assegnazioni-' . $anno->label . '.pdf',
+            ['Content-Type' => 'application/pdf']
+        );
+    }
+
     public function mount(): void
     {
         if ($this->filtroAnno === '') {
@@ -240,8 +348,14 @@ class Registro extends Component
             'anni' => AnnoTeocratico::orderByDesc('start_date')->get(),
             'zone' => Zona::attive()->orderBy('nome')->get(),
             'tipologie' => Tipologia::orderBy('nome')->get(),
-            'territori' => Territorio::attivi()->orderBy('numero')->get(),
-            'proclamatori' => Proclamatore::attivi()->orderBy('cognome')->orderBy('nome')->get(),
+            // Campi di scelta con ricerca della finestra di modifica. Ci sono
+            // anche i disattivati, non sceglibili: modificando una vecchia
+            // assegnazione il campo mostra comunque il nome giusto.
+            'opzioniTerritori' => Territorio::with(['zona', 'tipologia'])->get()
+                ->sortBy('numero', SORT_NATURAL)
+                ->map(fn (Territorio $t) => $t->opzioneScelta($t->attivo ? null : 'territorio disattivato'))
+                ->values()->all(),
+            'opzioniProclamatori' => Proclamatore::opzioniScelta(Proclamatore::all()),
             'campagne' => Campagna::orderByDesc('created_at')->get(),
         ]);
     }

app/Livewire/Richieste/ModuloRichiesta.php

@@ -0,0 +1,137 @@
+<?php
+
+namespace App\Livewire\Richieste;
+
+use App\Models\Richiesta;
+use App\Models\Setting;
+use App\Models\Territorio;
+use App\Services\RichiesteServizio;
+use Illuminate\Database\Eloquent\Builder;
+use Illuminate\Support\Facades\RateLimiter;
+use Illuminate\Support\Str;
+use Livewire\Attributes\Locked;
+use Livewire\Component;
+
+/**
+ * Il modulo pubblico (/richiesta, senza login): un proclamatore chiede un
+ * territorio nuovo o annuncia una riconsegna. L'unico dato già presente che
+ * mostra è l'elenco dei territori nella riconsegna, per il completamento
+ * automatico del numero: numero e zona, mai a chi è assegnato né se lo è.
+ * Nomi e altri dati non si vedono.
+ *
+ * Contro lo spam, tre difese che a chi compila davvero non costano niente:
+ * - un campo trappola ($sito) nascosto alle persone e riempito dai programmi;
+ * - un tempo minimo fra apertura e invio (i programmi inviano subito);
+ * - al massimo MASSIMO_ORA richieste all'ora per indirizzo.
+ * Nei primi due casi si risponde come se fosse andata bene, senza salvare:
+ * chi prova non impara cosa l'ha fermato.
+ */
+class ModuloRichiesta extends Component
+{
+    public const MASSIMO_ORA = 5;
+
+    public const SECONDI_MINIMI = 3;
+
+    public string $tipo = Richiesta::NUOVO;
+
+    public string $nome = '';
+
+    public string $numero = '';
+
+    public string $note = '';
+
+    /** Trappola: nascosto alle persone, i programmi lo riempiono. */
+    public string $sito = '';
+
+    #[Locked]
+    public int $apertoAlle = 0;
+
+    #[Locked]
+    public bool $inviata = false;
+
+    public function mount(): void
+    {
+        $this->apertoAlle = now()->timestamp;
+    }
+
+    public function invia(RichiesteServizio $richieste): void
+    {
+        if ($this->sito !== '' || now()->timestamp - $this->apertoAlle < self::SECONDI_MINIMI) {
+            $this->inviata = true;
+
+            return;
+        }
+
+        $chiave = 'richiesta-pubblica:' . sha1((string) request()->ip());
+        if (RateLimiter::tooManyAttempts($chiave, self::MASSIMO_ORA)) {
+            $this->addError('nome', "Hai già mandato diverse richieste: riprova fra un po'.");
+
+            return;
+        }
+
+        $this->validate([
+            'tipo' => 'required|in:' . Richiesta::NUOVO . ',' . Richiesta::RICONSEGNA,
+            'nome' => 'required|string|min:3|max:100',
+            'numero' => ['nullable', 'required_if:tipo,' . Richiesta::RICONSEGNA, 'string', 'max:20',
+                function ($attributo, $valore, $errore) {
+                    if ($this->tipo === Richiesta::RICONSEGNA && ! self::territori()->whereRaw('LOWER(numero) = ?', [Str::lower(trim((string) $valore))])->exists()) {
+                        $errore("Scegli il territorio dall'elenco.");
+                    }
+                }],
+            'note' => 'nullable|string|max:1000',
+        ], [
+            'nome.required' => 'Scrivi nome e cognome.',
+            'nome.min' => 'Scrivi nome e cognome.',
+            'numero.required_if' => 'Scegli il territorio che riconsegni.',
+        ]);
+
+        RateLimiter::hit($chiave, 3600);
+        $richieste->registra($this->tipo, $this->nome, $this->numero, $this->note);
+
+        $this->reset(['nome', 'numero', 'note']);
+        $this->inviata = true;
+    }
+
+    public function nuova(): void
+    {
+        $this->reset(['tipo', 'nome', 'numero', 'note', 'inviata']);
+        $this->apertoAlle = now()->timestamp;
+    }
+
+    /**
+     * I territori che si possono riconsegnare: quelli attivi e quelli ancora
+     * fuori anche se nel frattempo disattivati.
+     */
+    private static function territori(): Builder
+    {
+        return Territorio::query()->where(fn ($q) => $q->where('attivo', true)
+            ->orWhereHas('assegnazioni', fn ($a) => $a->whereNull('returned_at')));
+    }
+
+    /**
+     * Le proposte del campo con ricerca (<x-scelta>): solo numero e zona. Il
+     * valore è il numero, come lo salva la richiesta.
+     */
+    private static function opzioniTerritori(): array
+    {
+        return self::territori()->with('zona')->get()
+            ->sortBy('numero', SORT_NATURAL)
+            ->map(fn (Territorio $t) => array_filter([
+                'valore' => (string) $t->numero,
+                'etichetta' => "N° {$t->numero}",
+                'dettaglio' => $t->zona?->nome,
+                'chiavi' => [(string) $t->numero, (string) $t->zona?->nome],
+            ], fn ($v) => $v !== null))
+            ->values()
+            ->all();
+    }
+
+    public function render()
+    {
+        return view('livewire.richieste.modulo-richiesta', [
+            'congregazione' => Setting::instance()->congregazione_nome ?: 'TerManager2',
+            // Solo quando serve: chi chiede un territorio nuovo non vede l'elenco.
+            'opzioniTerritori' => $this->tipo === Richiesta::RICONSEGNA && ! $this->inviata ? self::opzioniTerritori() : [],
+        ])->layout('components.layouts.guest', ['title' => 'Richiesta territorio']);
+    }
+}

app/Livewire/Settings/BackupManager.php

@@ -0,0 +1,115 @@
+<?php
+
+namespace App\Livewire\Settings;
+
+use App\Jobs\CreateBackupArchive;
+use App\Livewire\Concerns\SegueOperazioneBackup;
+use App\Services\BackupOperationState;
+use Livewire\Component;
+
+/**
+ * Le due zone che si usano tutti i giorni: creare il pacchetto di backup e
+ * ripristinarlo.
+ *
+ * Il lavoro vero sta nei job; qui si avvia e si interroga lo stato. L'avanzamento
+ * e le righe di log non compaiono piu' in questa sezione: finiscono nella console
+ * unica agganciata in fondo alla pagina, che le riceve per eventi (vedi il trait
+ * SegueOperazioneBackup). Qui restano solo i comandi e l'esito.
+ *
+ * L'azzeramento sta in ZonaPericolosa, che e' un componente a se' perche' deve
+ * comparire in fondo alla pagina, dopo tutte le altre zone: dentro questa
+ * sezione finiva a meta' pagina, fra il ripristino e l'import.
+ */
+class BackupManager extends Component
+{
+    use SegueOperazioneBackup;
+
+    public function mount(): void
+    {
+        $this->authorize('settings.manage');
+
+        $this->agganciaOperazioneCorrente();
+    }
+
+    /**
+     * Backup e ripristino si raccontano da qui; l'azzeramento e' della zona
+     * pericolosa. Vedi SegueOperazioneBackup::tipiSeguiti().
+     */
+    protected function tipiSeguiti(): array
+    {
+        return [BackupOperationState::TIPO_BACKUP, BackupOperationState::TIPO_RESTORE];
+    }
+
+    public function avviaBackup(): void
+    {
+        $this->authorize('settings.manage');
+
+        if (! $this->postoLibero()) {
+            return;
+        }
+
+        $operationId = $this->nuovaOperazione(BackupOperationState::TIPO_BACKUP);
+        if ($operationId === null) {
+            return;
+        }
+        $this->operationId = $operationId;
+
+        CreateBackupArchive::dispatch($this->operationId, false);
+
+        $this->aggiorna();
+
+        $this->avvisaZonaPericolosa();
+    }
+
+    /**
+     * Aggancia un'operazione avviata fuori da Livewire: il ripristino parte da un
+     * upload XHR e restituisce il proprio id in JSON.
+     */
+    public function seguiOperazione(string $operationId): void
+    {
+        $this->authorize('settings.manage');
+
+        $this->operationId = $operationId;
+        $this->logSpediti = 0;
+        $this->aggiorna();
+
+        $this->avvisaZonaPericolosa();
+    }
+
+    /**
+     * Il posto e' uno solo: la zona pericolosa deve sapere che e' occupato,
+     * altrimenti continuerebbe a offrire il proprio pulsante durante un backup o
+     * un ripristino.
+     *
+     * L'evento e' indirizzato, non gridato: senza ->to() tornerebbe anche a
+     * questo componente, che si riaggancerebbe a un'operazione appena
+     * agganciata — una richiesta in piu' a ogni avvio, per niente.
+     */
+    private function avvisaZonaPericolosa(): void
+    {
+        $this->dispatch('operazione-avviata')->to(ZonaPericolosa::class);
+    }
+
+    /**
+     * L'azzeramento avviato dalla zona pericolosa non passa da qui, ma occupa lo
+     * stesso posto: senza riagganciarsi, questa sezione resterebbe convinta che
+     * sia libero e offrirebbe il pulsante "Crea backup" durante una
+     * cancellazione.
+     */
+    #[\Livewire\Attributes\On('operazione-avviata')]
+    public function agganciaAltrove(): void
+    {
+        $this->agganciaOperazioneCorrente();
+    }
+
+    /** Vero quando l'archivio di questa operazione e' scaricabile. */
+    public function getArchivioProntoProperty(): bool
+    {
+        return ($this->operazione['result']['file'] ?? null) !== null;
+    }
+
+    public function render()
+    {
+        return view('livewire.settings.backup-manager');
+    }
+}

app/Livewire/Settings/PostaElettronica.php

@@ -0,0 +1,132 @@
+<?php
+
+namespace App\Livewire\Settings;
+
+use App\Livewire\Concerns\Avvisa;
+use App\Models\Setting;
+use App\Services\ConfigurazionePosta;
+use Illuminate\Validation\Rule;
+use Livewire\Component;
+
+/**
+ * Server di posta (solo amministratore).
+ *
+ * Serve alle email di conferma degli utenti. Raggiungibile anche da un
+ * amministratore che non ha ancora confermato la sua email (vedi
+ * routes/web.php): se la posta non funziona, è l'unica pagina da cui
+ * sistemarla senza passare dal server.
+ */
+class PostaElettronica extends Component
+{
+    use Avvisa;
+
+    public string $host = '';
+
+    public string $porta = '';
+
+    public string $cifratura = ConfigurazionePosta::CIFRATURA_AUTOMATICA;
+
+    public string $utente = '';
+
+    /** Vuota = si tiene quella salvata. Non torna mai al browser. */
+    public string $password = '';
+
+    public string $mittente = '';
+
+    public string $nomeMittente = '';
+
+    public function mount(): void
+    {
+        $impostazioni = Setting::instance();
+
+        $this->host = (string) $impostazioni->mail_host;
+        $this->porta = (string) ($impostazioni->mail_port ?? '');
+        $this->cifratura = $impostazioni->mail_cifratura ?: ConfigurazionePosta::CIFRATURA_AUTOMATICA;
+        $this->utente = (string) $impostazioni->mail_username;
+        $this->mittente = (string) $impostazioni->mail_from_address;
+        $this->nomeMittente = (string) $impostazioni->mail_from_name;
+    }
+
+    public function salva(): void
+    {
+        $this->host = trim($this->host);
+        $this->mittente = trim($this->mittente);
+
+        $this->validate([
+            'host' => ['required', 'string', 'max:255', 'regex:/^[A-Za-z0-9.\-]+$/'],
+            'porta' => ['nullable', 'integer', 'min:1', 'max:65535'],
+            'cifratura' => ['required', Rule::in(array_keys(ConfigurazionePosta::CIFRATURE))],
+            'utente' => ['nullable', 'string', 'max:255'],
+            'password' => ['nullable', 'string', 'max:500'],
+            'mittente' => ['required', 'email', 'max:255'],
+            'nomeMittente' => ['nullable', 'string', 'max:255'],
+        ], [
+            'host.required' => 'Indica il server SMTP (es. smtp.gmail.com).',
+            'host.regex' => 'Solo il nome del server, senza "smtp://" né porta.',
+            'mittente.required' => 'Indica l\'indirizzo da cui partono le email.',
+            'mittente.email' => 'L\'indirizzo del mittente non è valido.',
+        ]);
+
+        $valori = [
+            'mail_host' => $this->host,
+            'mail_port' => $this->porta !== '' ? (int) $this->porta : null,
+            'mail_cifratura' => $this->cifratura,
+            'mail_username' => trim($this->utente) ?: null,
+            'mail_from_address' => $this->mittente,
+            'mail_from_name' => trim($this->nomeMittente) ?: null,
+        ];
+        if ($this->password !== '') {
+            $valori['mail_password'] = $this->password;
+        }
+
+        Setting::instance()->update($valori);
+        $this->password = '';
+
+        activity()->causedBy(auth()->user())->log('posta_configurata');
+        $this->avvisa('Server di posta salvato. Prova l\'invio con "Invia email di prova".');
+    }
+
+    public function inviaProva(ConfigurazionePosta $posta): void
+    {
+        if (! $posta->configurataNellApp()) {
+            $this->avvisaErrore('Salva prima il server di posta.');
+
+            return;
+        }
+
+        try {
+            $posta->inviaProva(auth()->user()->email);
+        } catch (\RuntimeException $e) {
+            $this->avvisaErrore($e->getMessage());
+
+            return;
+        }
+
+        $this->avvisa('Email di prova inviata a ' . auth()->user()->email . '. Controlla anche lo spam.');
+    }
+
+    /** Torna al server del .env. */
+    public function rimuovi(): void
+    {
+        Setting::instance()->update(array_fill_keys(Setting::CAMPI_POSTA, null));
+        $this->mount();
+        $this->password = '';
+
+        activity()->causedBy(auth()->user())->log('posta_rimossa');
+        $this->avvisa('Configurazione rimossa: valgono di nuovo le impostazioni del server (.env).');
+    }
+
+    public function render(ConfigurazionePosta $posta)
+    {
+        $impostazioni = Setting::instance();
+
+        return view('livewire.settings.posta-elettronica', [
+            'configurataNellApp' => $posta->configurataNellApp(),
+            'funzionante' => $posta->funzionante(),
+            'passwordSalvata' => $impostazioni->getRawOriginal('mail_password') !== null,
+            'cifrature' => ConfigurazionePosta::CIFRATURE,
+            'nonConfermato' => ! auth()->user()->hasVerifiedEmail(),
+            'title' => 'Server di posta',
+        ]);
+    }
+}

app/Livewire/Settings/SettingsEdit.php

@@ -2,17 +2,18 @@
 
 namespace App\Livewire\Settings;
 
+use App\Livewire\Concerns\Avvisa;
 use Livewire\Component;
 use App\Models\Setting;
 
 class SettingsEdit extends Component
 {
+    use Avvisa;
     public string $congregazione_nome = '';
     public int $giorni_giacenza_da_assegnare = 120;
     public int $giorni_giacenza_prioritari = 180;
     public int $giorni_per_smarrito = 120;
     public int $home_limit_list = 10;
-    public int $assignment_link_ttl_months = 1;
     public bool $pdf_viewer_show_download = true;
     public int $audit_retention_days = 365;
 
@@ -24,7 +25,6 @@ class SettingsEdit extends Component
         $this->giorni_giacenza_prioritari = $settings->giorni_giacenza_prioritari ?? 180;
         $this->giorni_per_smarrito = $settings->giorni_per_smarrito ?? 120;
         $this->home_limit_list = $settings->home_limit_list ?? 10;
-        $this->assignment_link_ttl_months = $settings->assignment_link_ttl_hours ?? 1;
         $this->pdf_viewer_show_download = $settings->pdf_viewer_show_download ?? true;
         $this->audit_retention_days = $settings->audit_retention_days ?? 365;
     }
@@ -37,7 +37,6 @@ class SettingsEdit extends Component
             'giorni_giacenza_prioritari' => 'required|integer|min:1|max:730',
             'giorni_per_smarrito' => 'required|integer|min:30|max:365',
             'home_limit_list' => 'required|integer|min:1|max:100',
-            'assignment_link_ttl_months' => 'required|integer|min:1|max:24',
             'pdf_viewer_show_download' => 'required|boolean',
             'audit_retention_days' => 'required|integer|min:30|max:3650',
         ];
@@ -54,12 +53,11 @@ class SettingsEdit extends Component
             'giorni_giacenza_prioritari' => $this->giorni_giacenza_prioritari,
             'giorni_per_smarrito' => $this->giorni_per_smarrito,
             'home_limit_list' => $this->home_limit_list,
-            'assignment_link_ttl_hours' => $this->assignment_link_ttl_months,
             'pdf_viewer_show_download' => $this->pdf_viewer_show_download,
             'audit_retention_days' => $this->audit_retention_days,
         ]);
 
-        session()->flash('success', 'Impostazioni aggiornate.');
+        $this->avvisa('Impostazioni aggiornate.');
     }
 
     public function render()

app/Livewire/Settings/TipologieIndex.php

@@ -2,11 +2,13 @@
 
 namespace App\Livewire\Settings;
 
+use App\Livewire\Concerns\Avvisa;
 use Livewire\Component;
 use App\Models\Tipologia;
 
 class TipologieIndex extends Component
 {
+    use Avvisa;
     public string $nuovaTipologia = '';
     public ?int $editingId = null;
     public string $editingNome = '';
@@ -16,7 +18,7 @@ class TipologieIndex extends Component
         $this->validate(['nuovaTipologia' => 'required|string|max:100|unique:tipologie,nome']);
         Tipologia::create(['nome' => $this->nuovaTipologia, 'attivo' => true]);
         $this->nuovaTipologia = '';
-        session()->flash('success', 'Tipologia aggiunta.');
+        $this->avvisa('Tipologia aggiunta.');
     }
 
     public function startEdit(int $id)
@@ -33,7 +35,7 @@ class TipologieIndex extends Component
         $tipo->update(['nome' => $this->editingNome]);
         $this->editingId = null;
         $this->editingNome = '';
-        session()->flash('success', 'Tipologia aggiornata.');
+        $this->avvisa('Tipologia aggiornata.');
     }
 
     public function cancelEdit()
@@ -52,11 +54,11 @@ class TipologieIndex extends Component
     {
         $tipo = Tipologia::findOrFail($id);
         if ($tipo->territori()->exists()) {
-            session()->flash('error', "Impossibile eliminare: la tipologia '{$tipo->nome}' ha territori associati.");
+            $this->avvisaErrore("Impossibile eliminare: la tipologia '{$tipo->nome}' ha territori associati.");
             return;
         }
         $tipo->delete();
-        session()->flash('success', "Tipologia '{$tipo->nome}' eliminata.");
+        $this->avvisa("Tipologia '{$tipo->nome}' eliminata.");
     }
 
     public function render()

app/Livewire/Settings/UsersIndex.php

@@ -2,23 +2,40 @@
 
 namespace App\Livewire\Settings;
 
-use App\Models\Assegnazione;
+use App\Livewire\Concerns\Avvisa;
+use App\Models\GruppoServizio;
 use App\Models\User;
-use Illuminate\Support\Facades\DB;
+use App\Services\GruppiServizio;
 use Illuminate\Validation\Rule;
+use InvalidArgumentException;
+use Livewire\Attributes\Locked;
 use Livewire\Component;
-use Spatie\Activitylog\Models\Activity;
 use Spatie\Permission\Models\Role;
 
 class UsersIndex extends Component
 {
+    use Avvisa;
     public string $name = '';
     public string $email = '';
     public string $password = '';
     public string $password_confirmation = '';
     public string $selectedRole = '';
+    // Locked: è la lista che le regole di validazione usano per accettare un
+    // ruolo; modificabile dal client, ammetterebbe qualsiasi nome.
+    #[Locked]
     public array $availableRoles = [];
 
+    /**
+     * Nuova password temporanea di un sorvegliante di gruppo, mostrata una
+     * volta sola (come nella pagina del gruppo). Locked: le scrive solo
+     * nuovaPasswordSorvegliante().
+     */
+    #[Locked]
+    public ?int $passwordPerUtenteId = null;
+
+    #[Locked]
+    public ?string $passwordTemporanea = null;
+
     public ?int $editingUserId = null;
     public string $editName = '';
     public string $editEmail = '';
@@ -28,7 +45,10 @@ class UsersIndex extends Component
 
     public function mount(): void
     {
+        // "sorvegliante" si dà solo creando un gruppo di servizio, con
+        // l'utenza collegata al proclamatore: da qui non si assegna.
         $this->availableRoles = Role::query()
+            ->where('name', '!=', 'sorvegliante')
             ->orderBy('name')
             ->pluck('name')
             ->all();
@@ -79,12 +99,54 @@ class UsersIndex extends Component
         if (! empty($this->availableRoles)) {
             $this->selectedRole = $this->availableRoles[0];
         }
-        session()->flash('success', 'Utente creato con successo.');
+
+        // L'account funziona solo dopo la conferma dell'indirizzo.
+        if ($user->inviaConfermaEmail()) {
+            $this->avvisa("Utente creato. Gli è stata inviata un'email a {$user->email}: l'account funziona dopo che conferma l'indirizzo.");
+        } else {
+            $this->avvisaErrore("Utente creato, ma l'email di conferma non è partita: controlla il server di posta e usa \"Reinvia conferma\".");
+        }
+    }
+
+    public function reinviaConferma(int $userId): void
+    {
+        $user = User::query()->findOrFail($userId);
+
+        if ($user->hasVerifiedEmail()) {
+            $this->avvisa("{$user->email} è già confermato.");
+
+            return;
+        }
+
+        if ($user->inviaConfermaEmail()) {
+            $this->avvisa("Email di conferma inviata a {$user->email}.");
+        } else {
+            $this->avvisaErrore('L\'email non è partita: controlla il server di posta.');
+        }
+    }
+
+    /**
+     * Le utenze dei sorveglianti di gruppo si gestiscono
+     * da Gruppi di servizio: cambiarle o cancellarle da qui lascerebbe un
+     * gruppo senza sorvegliante, o un sorvegliante con un ruolo diverso.
+     */
+    private function gestitaDaiGruppi(User $user): bool
+    {
+        if ($user->proclamatore_id === null) {
+            return false;
+        }
+
+        $this->avvisaErrore("L'utenza di {$user->name} è di un sorvegliante di gruppo: si gestisce da Gruppi di servizio.");
+
+        return true;
     }
 
     public function startEdit(int $userId): void
     {
         $user = User::query()->with('roles')->findOrFail($userId);
+        if ($this->gestitaDaiGruppi($user)) {
+            return;
+        }
 
         $this->editingUserId = $user->id;
         $this->editName = $user->name;
@@ -114,6 +176,26 @@ class UsersIndex extends Component
 
         $validated = $this->validate($this->editRules());
         $user = User::query()->findOrFail($this->editingUserId);
+        if ($this->gestitaDaiGruppi($user)) {
+            return;
+        }
+
+        // Togliere il ruolo di amministratore a sé stessi, o all'ultimo
+        // rimasto, lascia l'installazione senza nessuno che possa gestire
+        // utenti, impostazioni e backup.
+        if ($user->hasRole('amministratore') && $validated['editSelectedRole'] !== 'amministratore') {
+            if ($user->id === auth()->id()) {
+                $this->addError('editSelectedRole', 'Non puoi togliere a te stesso il ruolo di amministratore: chiedilo a un altro amministratore.');
+
+                return;
+            }
+
+            if (User::role('amministratore')->count() <= 1) {
+                $this->addError('editSelectedRole', "È l'ultimo amministratore: assegna prima il ruolo a un altro utente.");
+
+                return;
+            }
+        }
 
         $user->name = $validated['editName'];
         $user->email = $validated['editEmail'];
@@ -122,71 +204,87 @@ class UsersIndex extends Component
             $user->password = $validated['editPassword'];
         }
 
+        $emailCambiata = $user->isDirty('email');
         $user->save();
         $user->syncRoles([$validated['editSelectedRole']]);
 
         $this->cancelEdit();
-        session()->flash('success', 'Utente aggiornato con successo.');
+
+        // Indirizzo nuovo: torna da confermare (User::booted) e gli si manda
+        // il link, altrimenti il suo account smetterebbe di funzionare senza
+        // che sappia perché.
+        if ($emailCambiata) {
+            $inviata = $user->inviaConfermaEmail();
+            $inviata
+                ? $this->avvisa("Utente aggiornato. Il nuovo indirizzo va confermato: email inviata a {$user->email}.")
+                : $this->avvisaErrore('Utente aggiornato, ma l\'email di conferma del nuovo indirizzo non è partita: controlla il server di posta.');
+
+            return;
+        }
+
+        $this->avvisa('Utente aggiornato con successo.');
     }
 
     public function deleteUser(int $userId): void
     {
         $currentUser = auth()->user();
         $user = User::query()->with('roles')->findOrFail($userId);
+        if ($this->gestitaDaiGruppi($user)) {
+            return;
+        }
 
         if (! $currentUser || $currentUser->id === $user->id) {
-            session()->flash('error', 'Non puoi cancellare il tuo utente.');
+            $this->avvisaErrore('Non puoi cancellare il tuo utente.');
             return;
         }
 
         if ($user->hasRole('amministratore') && User::role('amministratore')->count() <= 1) {
-            session()->flash('error', 'Non puoi cancellare l\'ultimo amministratore.');
+            $this->avvisaErrore('Non puoi cancellare l\'ultimo amministratore.');
             return;
         }
 
-        DB::transaction(function () use ($user, $currentUser) {
-            $causerName = $user->name;
-            $causerEmail = $user->email;
-            $deletedAt = now()->toDateTimeString();
-
-            Activity::query()
-                ->where('causer_type', User::class)
-                ->where('causer_id', $user->id)
-                ->chunkById(200, function ($activities) use ($causerName, $causerEmail, $deletedAt) {
-                    foreach ($activities as $activity) {
-                        $properties = $activity->properties?->toArray() ?? [];
-                        $properties['causer_name'] = $causerName;
-                        $properties['causer_email'] = $causerEmail;
-                        $properties['causer_deleted_at'] = $deletedAt;
-
-                        $activity->properties = $properties;
-                        $activity->save();
-                    }
-                });
-
-            Assegnazione::query()
-                ->where('created_by', $user->id)
-                ->update(['created_by' => $currentUser->id]);
-
-            Assegnazione::query()
-                ->where('returned_by', $user->id)
-                ->update(['returned_by' => $currentUser->id]);
-
-            $user->syncRoles([]);
-            $user->delete();
-        });
+        $user->eliminaConservandoStorico($currentUser, $user->name, $user->email);
 
         if ($this->editingUserId === $userId) {
             $this->cancelEdit();
         }
 
-        session()->flash('success', 'Utente cancellato. I log sono stati preservati.');
+        $this->avvisa('Utente cancellato. I log sono stati preservati.');
+    }
+
+    /**
+     * Il sorvegliante ha perso la password: una temporanea nuova, da cambiare
+     * al primo accesso. È l'unica cosa che di quell'utenza si fa da qui; il
+     * resto passa dal gruppo (gestitaDaiGruppi).
+     */
+    public function nuovaPasswordSorvegliante(int $userId): void
+    {
+        $this->authorize('settings.manage');
+        $user = User::query()->findOrFail($userId);
+
+        try {
+            $this->passwordTemporanea = app(GruppiServizio::class)->nuovaPasswordTemporanea($user);
+        } catch (InvalidArgumentException $e) {
+            $this->avvisaErrore($e->getMessage());
+
+            return;
+        }
+
+        $this->passwordPerUtenteId = $user->id;
+    }
+
+    public function chiudiPassword(): void
+    {
+        $this->reset(['passwordPerUtenteId', 'passwordTemporanea']);
     }
 
     public function render()
     {
         return view('livewire.settings.users-index', [
             'users' => User::query()->with('roles')->orderBy('name')->get(),
+            // Per ogni sorvegliante il suo gruppo, per il collegamento.
+            'gruppiDeiSorveglianti' => GruppoServizio::pluck('id', 'sorvegliante_id'),
+            'utentePassword' => $this->passwordPerUtenteId ? User::find($this->passwordPerUtenteId) : null,
         ]);
     }
 }

app/Livewire/Settings/ZonaPericolosa.php

@@ -0,0 +1,256 @@
+<?php
+
+namespace App\Livewire\Settings;
+
+use App\Jobs\CreateBackupArchive;
+use App\Jobs\ResetApplication;
+use App\Livewire\Concerns\SegueOperazioneBackup;
+use App\Services\BackupOperationState;
+use Illuminate\Support\Facades\Hash;
+use Illuminate\Support\Facades\RateLimiter;
+use Livewire\Component;
+
+/**
+ * Azzeramento dell'applicazione: l'unica operazione irreversibile della pagina,
+ * e per questo l'ultima zona, dopo tutte le altre.
+ *
+ * E' un componente separato da BackupManager per una ragione di sola
+ * disposizione: la zona pericolosa deve stare in fondo alla pagina, mentre le
+ * sezioni di backup e ripristino stanno in cima. Rendendola dallo stesso
+ * componente finiva a meta' pagina, in mezzo alle sezioni di import, che e'
+ * l'ultimo posto in cui si vuole trovare un pulsante che cancella tutto.
+ *
+ * Lo stato dell'operazione resta condiviso con BackupManager attraverso
+ * BackupOperationState (il trait), quindi i due non hanno bisogno di parlarsi per
+ * restare coerenti: il posto unico e' uno solo per entrambi.
+ *
+ * L'azzeramento ha due tempi, separati dal download dell'archivio:
+ *
+ *   1. avviaAzzeramento()    crea il backup e si ferma in attesa-download
+ *   2. confermaAzzeramento() cancella, solo su conferma umana e con la password
+ *
+ * Il primo tentativo faceva partire la cancellazione dalla coda dello
+ * streamDownload, "dopo l'ultimo byte": non funziona. Con fastcgi_buffering
+ * attivo (il default) nginx accetta l'intera risposta dal processo PHP, che
+ * prosegue anche se il browser ha chiuso la connessione al primo byte, quindi un
+ * download annullato azzerava lo stesso. Il server puo' verificare di aver
+ * *spedito* l'archivio, non che sia arrivato: quella verifica e' dell'operatore,
+ * e per questo la conferma e' umana.
+ */
+class ZonaPericolosa extends Component
+{
+    use SegueOperazioneBackup;
+
+    /** Frase da digitare per sbloccare l'azzeramento. */
+    public const CONFERMA_AZZERAMENTO = 'AZZERA TUTTO';
+
+    /** Password sbagliate ammesse prima di bloccare l'azzeramento, e per quanto. */
+    private const TENTATIVI_PASSWORD = 5;
+    private const FINESTRA_TENTATIVI = 300;
+
+    public string $confermaReset = '';
+
+    /**
+     * Esiste solo per dare un nome agli errori del campo password: Livewire
+     * scarta dal messaggio di risposta ogni errore la cui chiave non
+     * corrisponda a una proprieta' del componente (SupportValidation::dehydrate),
+     * quindi senza questa riga "Password non corretta" non arriverebbe mai a
+     * schermo e il pulsante sembrerebbe non fare nulla.
+     *
+     * NON collegarla al campo con wire:model: la password viaggia come
+     * parametro di confermaAzzeramento() proprio per non finire nello
+     * snapshot, che Livewire rimanda al browser a ogni risposta. Qui resta
+     * sempre stringa vuota.
+     */
+    public string $passwordConferma = '';
+
+    public function mount(): void
+    {
+        $this->authorize('settings.manage');
+
+        $this->agganciaOperazioneCorrente();
+    }
+
+    /**
+     * Solo l'azzeramento: backup e ripristino li racconta BackupManager. Vedi
+     * SegueOperazioneBackup::tipiSeguiti().
+     */
+    protected function tipiSeguiti(): array
+    {
+        return [BackupOperationState::TIPO_RESET];
+    }
+
+    /**
+     * Primo tempo: si costruisce il backup e lo si scarica. La cancellazione non
+     * parte da qui.
+     */
+    public function avviaAzzeramento(): void
+    {
+        $this->authorize('settings.manage');
+
+        $this->validate(
+            ['confermaReset' => 'required|in:' . self::CONFERMA_AZZERAMENTO],
+            ['confermaReset.in' => 'Scrivi esattamente "' . self::CONFERMA_AZZERAMENTO . '" per confermare.',
+             'confermaReset.required' => 'Scrivi "' . self::CONFERMA_AZZERAMENTO . '" per confermare.']
+        );
+
+        if (! $this->postoLibero()) {
+            return;
+        }
+
+        $operationId = $this->nuovaOperazione(BackupOperationState::TIPO_RESET);
+        if ($operationId === null) {
+            return;
+        }
+
+        $this->confermaReset = '';
+        $this->operationId = $operationId;
+
+        CreateBackupArchive::dispatch($this->operationId, true);
+
+        $this->aggiorna();
+
+        // La sezione di backup deve sapere che il posto e' occupato, altrimenti
+        // continuerebbe a offrire il proprio pulsante durante l'azzeramento.
+        // Indirizzato e non gridato: senza ->to() l'evento tornerebbe anche qui.
+        $this->dispatch('operazione-avviata')->to(BackupManager::class);
+    }
+
+    /**
+     * Secondo tempo: parte solo su conferma esplicita, dopo che l'archivio e'
+     * stato servito.
+     */
+    public function confermaAzzeramento(string $password = ''): void
+    {
+        $this->authorize('settings.manage');
+
+        $this->aggiorna();
+
+        if (! $this->attesaDownload) {
+            $this->addError('confermaReset', 'Nessun azzeramento in attesa di conferma.');
+
+            return;
+        }
+
+        if (($this->operazione['result']['servito_at'] ?? null) === null) {
+            $this->addError('confermaReset', 'Scarica prima il backup: senza, l\'azzeramento non parte.');
+
+            return;
+        }
+
+        if (! $this->passwordConfermata($password)) {
+            return;
+        }
+
+        app(BackupOperationState::class)->update($this->operationId, function (array $state) {
+            $state['fase'] = 'Azzeramento in avvio';
+            $state['processed'] = 0;
+            $state['total'] = 0;
+
+            return $state;
+        });
+
+        ResetApplication::dispatch($this->operationId, (int) auth()->id());
+
+        $this->aggiorna();
+    }
+
+    /**
+     * Verifica la password dell'amministratore prima della cancellazione.
+     *
+     * A questo punto la sessione e' gia' autenticata, quindi la password non
+     * serve a stabilire *chi* sia: serve a stabilire che davanti allo schermo
+     * ci sia ancora quella persona. E' l'ultimo passo prima di un'operazione
+     * irreversibile, e una scheda lasciata aperta su una postazione condivisa e'
+     * lo scenario esatto contro cui protegge.
+     */
+    private function passwordConfermata(string $password): bool
+    {
+        $utente = auth()->user();
+        $chiave = 'azzeramento-password:' . $utente->id;
+
+        // Senza un limite, la richiesta di password su una sessione dirottata
+        // sarebbe solo un rallentamento: si proverebbero le password comuni a
+        // raffica. Il blocco e' sull'azione, non sull'account, quindi nessuno
+        // resta chiuso fuori dall'applicazione.
+        if (RateLimiter::tooManyAttempts($chiave, self::TENTATIVI_PASSWORD)) {
+            $this->addError('passwordConferma', sprintf(
+                'Troppi tentativi. Riprova fra %d secondi.',
+                RateLimiter::availableIn($chiave)
+            ));
+
+            return false;
+        }
+
+        if ($password === '') {
+            $this->addError('passwordConferma', 'Inserisci la tua password per confermare.');
+
+            return false;
+        }
+
+        if (! Hash::check($password, $utente->getAuthPassword())) {
+            RateLimiter::hit($chiave, self::FINESTRA_TENTATIVI);
+            $this->addError('passwordConferma', 'Password non corretta.');
+
+            return false;
+        }
+
+        RateLimiter::clear($chiave);
+
+        return true;
+    }
+
+    /**
+     * Annulla un azzeramento fermo in attesa di conferma. Il backup resta
+     * scaricabile: e' comunque un backup valido.
+     */
+    public function annullaAzzeramento(): void
+    {
+        $this->authorize('settings.manage');
+
+        if (! $this->attesaDownload) {
+            return;
+        }
+
+        app(BackupOperationState::class)->markCompleted($this->operationId, [
+            'messaggio' => 'Azzeramento annullato. Il backup appena creato resta scaricabile.',
+        ]);
+
+        // Da qui in poi e' un backup come un altro: la sezione di backup mostra il
+        // pulsante di download, non piu' la conferma di cancellazione.
+        app(BackupOperationState::class)->update($this->operationId, function (array $state) {
+            $state['tipo'] = BackupOperationState::TIPO_BACKUP;
+
+            return $state;
+        });
+
+        $this->aggiorna();
+        $this->dispatch('operazione-avviata')->to(BackupManager::class);
+    }
+
+    /**
+     * Un azzeramento avviato altrove non esiste, ma il posto puo' essere occupato
+     * da un backup o da un ripristino: la zona deve saperlo per non offrire un
+     * pulsante che verrebbe rifiutato.
+     */
+    #[\Livewire\Attributes\On('operazione-avviata')]
+    public function agganciaAltrove(): void
+    {
+        $this->agganciaOperazioneCorrente();
+    }
+
+    /**
+     * Vero quando questa zona sta seguendo un azzeramento (non un backup o un
+     * ripristino avviati altrove).
+     */
+    public function getAzzeramentoInCorsoProperty(): bool
+    {
+        return $this->operationId !== null
+            && ($this->operazione['tipo'] ?? null) === BackupOperationState::TIPO_RESET;
+    }
+
+    public function render()
+    {
+        return view('livewire.settings.zona-pericolosa');
+    }
+}

app/Livewire/Settings/ZoneIndex.php

@@ -2,11 +2,13 @@
 
 namespace App\Livewire\Settings;
 
+use App\Livewire\Concerns\Avvisa;
 use Livewire\Component;
 use App\Models\Zona;
 
 class ZoneIndex extends Component
 {
+    use Avvisa;
     public string $nuovaZona = '';
     public ?int $editingId = null;
     public string $editingNome = '';
@@ -16,7 +18,7 @@ class ZoneIndex extends Component
         $this->validate(['nuovaZona' => 'required|string|max:100|unique:zone,nome']);
         Zona::create(['nome' => $this->nuovaZona, 'attivo' => true]);
         $this->nuovaZona = '';
-        session()->flash('success', 'Zona aggiunta.');
+        $this->avvisa('Zona aggiunta.');
     }
 
     public function startEdit(int $id)
@@ -33,7 +35,7 @@ class ZoneIndex extends Component
         $zona->update(['nome' => $this->editingNome]);
         $this->editingId = null;
         $this->editingNome = '';
-        session()->flash('success', 'Zona aggiornata.');
+        $this->avvisa('Zona aggiornata.');
     }
 
     public function cancelEdit()
@@ -52,11 +54,11 @@ class ZoneIndex extends Component
     {
         $zona = Zona::findOrFail($id);
         if ($zona->territori()->exists()) {
-            session()->flash('error', "Impossibile eliminare: la zona '{$zona->nome}' ha territori associati.");
+            $this->avvisaErrore("Impossibile eliminare: la zona '{$zona->nome}' ha territori associati.");
             return;
         }
         $zona->delete();
-        session()->flash('success', "Zona '{$zona->nome}' eliminata.");
+        $this->avvisa("Zona '{$zona->nome}' eliminata.");
     }
 
     public function render()

app/Livewire/Territori/TerritorioCestino.php

@@ -2,38 +2,72 @@
 
 namespace App\Livewire\Territori;
 
+use App\Livewire\Concerns\Avvisa;
 use Livewire\Component;
 use Livewire\WithPagination;
 use App\Models\Territorio;
+use App\Services\TerritorioThumbnailService;
+use Illuminate\Support\Facades\Storage;
 
 class TerritorioCestino extends Component
 {
+    use Avvisa;
     use WithPagination;
 
     public function restore(int $id)
     {
+        $this->authorize('territori.manage');
+
         $territorio = Territorio::onlyTrashed()->findOrFail($id);
         $territorio->restore();
         activity()->causedBy(auth()->user())
             ->performedOn($territorio)
             ->log('restored');
-        session()->flash('success', "Territorio {$territorio->numero} ripristinato.");
+        $this->avvisa("Territorio {$territorio->numero} ripristinato.");
     }
 
     public function forceDelete(int $id)
     {
+        $this->authorize('territori.manage');
+
         $territorio = Territorio::onlyTrashed()->findOrFail($id);
 
         if ($territorio->assegnazioni()->exists()) {
-            session()->flash('error', 'Impossibile eliminare definitivamente: il territorio ha assegnazioni nello storico.');
+            $this->avvisaErrore('Impossibile eliminare definitivamente: il territorio ha assegnazioni nello storico.');
             return;
         }
 
         activity()->causedBy(auth()->user())
             ->withProperties(['numero' => $territorio->numero])
             ->log('force_deleted_territorio');
+
+        // I file vanno via con la riga. Cancellare solo il record lascerebbe la
+        // mappa e la miniatura sul volume senza piu' nulla che le riferisca:
+        // invisibili in ogni schermata, non raggiungibili da nessuna
+        // cancellazione futura, e comunque dentro ogni backup successivo.
+        // Prima della riga, non dopo: se la cancellazione dei file fallisce,
+        // il territorio resta nel cestino e l'operazione si puo' ritentare.
+        $this->rimuoviFile($territorio);
+
         $territorio->forceDelete();
-        session()->flash('success', 'Territorio eliminato definitivamente.');
+        $this->avvisa('Territorio eliminato definitivamente.');
+    }
+
+    /**
+     * Rimuove mappa e miniatura di un territorio dal disco `public`.
+     *
+     * Stessa coppia di cancellazioni che fa TerritorioEdit quando si sostituisce
+     * il PDF; qui e' definitiva perche' non resta una riga a cui riattaccarle.
+     */
+    private function rimuoviFile(Territorio $territorio): void
+    {
+        if ($territorio->pdf_path) {
+            Storage::disk('public')->delete($territorio->pdf_path);
+        }
+
+        if ($territorio->thumbnail_path) {
+            app(TerritorioThumbnailService::class)->delete($territorio->thumbnail_path);
+        }
     }
 
     public function render()

app/Livewire/Territori/TerritorioCreate.php

@@ -2,6 +2,7 @@
 
 namespace App\Livewire\Territori;
 
+use App\Livewire\Concerns\RicordaRitorno;
 use Livewire\Component;
 use Livewire\WithFileUploads;
 use App\Models\Territorio;
@@ -11,6 +12,8 @@ use App\Services\TerritorioThumbnailService;
 
 class TerritorioCreate extends Component
 {
+    use RicordaRitorno;
+
     use WithFileUploads;
 
     public string $numero = '';
@@ -36,6 +39,8 @@ class TerritorioCreate extends Component
 
     public function save()
     {
+        $this->authorize('territori.manage');
+
         $this->validate();
 
         $data = [
@@ -62,7 +67,7 @@ class TerritorioCreate extends Component
             ->log('created');
 
         session()->flash('success', "Territorio {$territorio->numero} creato.");
-        return redirect()->route('territori.index');
+        return redirect()->to($this->destinazione(route('territori.index')));
     }
 
     public function render()

app/Livewire/Territori/TerritorioEdit.php

@@ -2,6 +2,7 @@
 
 namespace App\Livewire\Territori;
 
+use App\Livewire\Concerns\RicordaRitorno;
 use Livewire\Component;
 use Livewire\WithFileUploads;
 use App\Models\Territorio;
@@ -12,6 +13,8 @@ use Illuminate\Support\Facades\Storage;
 
 class TerritorioEdit extends Component
 {
+    use RicordaRitorno;
+
     use WithFileUploads;
 
     public Territorio $territorio;
@@ -49,6 +52,8 @@ class TerritorioEdit extends Component
 
     public function save()
     {
+        $this->authorize('territori.manage');
+
         $this->validate();
 
         $data = [
@@ -62,14 +67,17 @@ class TerritorioEdit extends Component
 
         if ($this->pdf) {
             $thumbService = app(TerritorioThumbnailService::class);
-            // Remove old PDF and thumbnail
-            if ($this->territorio->pdf_path) {
-                Storage::disk('public')->delete($this->territorio->pdf_path);
-            }
-            if ($this->territorio->thumbnail_path) {
-                $thumbService->delete($this->territorio->thumbnail_path);
-            }
+            // Prima il nuovo, poi il vecchio nello storico (ripristinabile
+            // dalla pagina Piantine). Prima il vecchio si cancellava subito:
+            // un caricamento sbagliato non si poteva disfare, e con il
+            // salvataggio fallito il territorio restava senza PDF.
             $pdfPath = $this->pdf->store('territori-pdf', 'public');
+            if (! $pdfPath) {
+                $this->addError('pdf', 'Non è stato possibile salvare il PDF: quello in uso non è stato toccato.');
+
+                return;
+            }
+            app(\App\Services\Piantine\PiantinaPdfService::class)->archiviaCorrente($this->territorio, 'manuale');
             $data['pdf_path'] = $pdfPath;
             $data['thumbnail_path'] = $thumbService->generate($pdfPath);
         }
@@ -77,11 +85,13 @@ class TerritorioEdit extends Component
         $this->territorio->update($data);
 
         session()->flash('success', "Territorio {$this->territorio->numero} aggiornato.");
-        return redirect()->route('territori.show', $this->territorio);
+        return redirect()->to($this->destinazione(route('territori.show', $this->territorio)));
     }
 
     public function removePdf()
     {
+        $this->authorize('territori.manage');
+
         if ($this->territorio->pdf_path) {
             Storage::disk('public')->delete($this->territorio->pdf_path);
             if ($this->territorio->thumbnail_path) {

app/Livewire/Territori/TerritorioIndex.php

@@ -2,7 +2,9 @@
 
 namespace App\Livewire\Territori;
 
+use App\Livewire\Concerns\Avvisa;
 use Illuminate\Pagination\LengthAwarePaginator;
+use Livewire\Attributes\Url;
 use Livewire\Component;
 use Livewire\WithPagination;
 use App\Models\Territorio;
@@ -11,16 +13,28 @@ use App\Models\Tipologia;
 
 class TerritorioIndex extends Component
 {
+    use Avvisa;
     use WithPagination;
 
+    // Ricerca, filtri e ordinamento stanno nell'indirizzo (#[Url]): tornando
+    // da una scheda o da un'operazione l'elenco si ritrova com'era.
+    #[Url(except: '')]
     public string $search = '';
+    #[Url(except: '')]
     public string $filterZona = '';
+    #[Url(except: '')]
     public string $filterTipologia = '';
+    #[Url(except: '')]
     public string $filterStato = '';
+    #[Url(except: '')]
     public string $filterPriorita = '';
+    #[Url(except: '')]
     public string $filterPdf = '';
+    #[Url(except: '')]
     public string $filterContenuti = '';
+    #[Url(except: 'numero')]
     public string $sortField = 'numero';
+    #[Url(except: 'asc')]
     public string $sortDirection = 'asc';
 
     protected $queryString = [
@@ -96,6 +110,11 @@ class TerritorioIndex extends Component
 
     public function toggleActive(Territorio $territorio)
     {
+        // La lista è ora visibile agli utenti operativi (territori.assign), ma
+        // modificare/eliminare i territori resta riservato all'amministratore.
+        // Il check DEVE stare nel metodo: la rotta index non lo garantisce più.
+        $this->authorize('territori.manage');
+
         $territorio->update(['attivo' => !$territorio->attivo]);
         activity()->causedBy(auth()->user())
             ->performedOn($territorio)
@@ -105,6 +124,8 @@ class TerritorioIndex extends Component
 
     public function togglePriority(Territorio $territorio)
     {
+        $this->authorize('territori.manage');
+
         $territorio->update(['prioritario' => !$territorio->prioritario]);
         activity()->causedBy(auth()->user())
             ->performedOn($territorio)
@@ -114,11 +135,13 @@ class TerritorioIndex extends Component
 
     public function deleteTerritorio(Territorio $territorio)
     {
+        $this->authorize('territori.manage');
+
         activity()->causedBy(auth()->user())
             ->performedOn($territorio)
             ->log('soft_deleted');
         $territorio->delete();
-        session()->flash('success', "Territorio {$territorio->numero} spostato nel cestino.");
+        $this->avvisa("Territorio {$territorio->numero} spostato nel cestino.");
     }
 
     public function render()
@@ -132,6 +155,7 @@ class TerritorioIndex extends Component
             'tipologia',
             'assegnazioneCorrente.proclamatore',
             'ultimaAssegnazione',
+            'gruppo',
         ]);
 
         if ($this->search) {
@@ -156,6 +180,7 @@ class TerritorioIndex extends Component
         if ($this->filterStato) {
             match ($this->filterStato) {
                 'in_reparto' => $query->inReparto(),
+                'in_gruppo' => $query->inGruppo(),
                 'assegnato' => $query->assegnato(),
                 'da_rientrare' => $query->daRientrare(),
                 'inattivo' => $query->where('attivo', false),

app/Livewire/Territori/TerritorioShow.php

@@ -2,13 +2,15 @@
 
 namespace App\Livewire\Territori;
 
+use App\Livewire\Concerns\RicordaRitorno;
 use Livewire\Component;
 use App\Models\Territorio;
 use App\Models\Assegnazione;
-use App\Models\Setting;
 
 class TerritorioShow extends Component
 {
+    use RicordaRitorno;
+
     public Territorio $territorio;
 
     public function mount(Territorio $territorio)
@@ -21,12 +23,15 @@ class TerritorioShow extends Component
         $assegnazioni = Assegnazione::where('territorio_id', $this->territorio->id)
             ->with(['proclamatore', 'annoTeocratico', 'campagna', 'creatoDa', 'rientratoDa'])
             ->orderByDesc('assigned_at')
+            ->orderByDesc('id')
             ->get()
-            ->groupBy(fn($a) => $a->annoTeocratico->label);
+            ->groupBy(fn($a) => $a->annoTeocratico->label)
+            // Dal più recente: gli anni ("2026-2027") si ordinano come testo.
+            ->sortKeysDesc();
 
         return view('livewire.territori.territorio-show', [
             'activeAssignment' => $this->territorio->assegnazioneCorrente,
-            'assignmentLinkTtlMonths' => (int) Setting::getValue('assignment_link_ttl_hours', 1),
+            'assignmentScadenza' => $this->territorio->assegnazioneCorrente?->data_consegna_presunta,
             'assegnazioniPerAnno' => $assegnazioni,
         ]);
     }

app/Mail/ModuloS13Mail.php

@@ -0,0 +1,50 @@
+<?php
+
+namespace App\Mail;
+
+use App\Models\AnnoTeocratico;
+use App\Models\User;
+use Illuminate\Mail\Attachment;
+use Illuminate\Mail\Mailable;
+use Illuminate\Mail\Mailables\Content;
+use Illuminate\Mail\Mailables\Envelope;
+
+/**
+ * Il modulo S-13 in PDF per un amministratore (registro:invia-s13). Non va in
+ * coda (niente ShouldQueue): il PDF contiene i nomi dei proclamatori, che in
+ * coda starebbero in chiaro.
+ */
+class ModuloS13Mail extends Mailable
+{
+    public function __construct(
+        public User $utente,
+        public AnnoTeocratico $anno,
+        private string $pdf,
+    ) {}
+
+    public function nomeFile(): string
+    {
+        return "S-13-registro-assegnazioni-{$this->anno->label}.pdf";
+    }
+
+    public function envelope(): Envelope
+    {
+        return new Envelope(subject: "Modulo S-13 — anno di servizio {$this->anno->label}");
+    }
+
+    public function content(): Content
+    {
+        return new Content(
+            text: 'mail.modulo-s13',
+            with: ['data' => now()->format('d/m/Y')],
+        );
+    }
+
+    /** @return array<int, Attachment> */
+    public function attachments(): array
+    {
+        return [
+            Attachment::fromData(fn () => $this->pdf, $this->nomeFile())->withMime('application/pdf'),
+        ];
+    }
+}