@hegemonart/get-design-done 1.34.2 → 1.34.4

package/.claude-plugin/marketplace.json

@@ -5,14 +5,14 @@
   },
   "metadata": {
     "description": "Get Design Done — 5-stage agent-orchestrated design pipeline with 9 connections, handoff-first workflow, bidirectional Figma write-back, 22+ specialized agents, queryable knowledge layer (intel store, dependency analysis, learnings extraction), and a self-improvement loop (reflector, frontmatter + budget feedback, global-skills layer). v1.20.0 ships the SDK foundation: gdd-state MCP server (11 typed tools), lockfile-safe STATE.md mutations, event stream, and resilience primitives (jittered-backoff, rate-guard, error-classifier, iteration-budget) for rate-limit + 429 + context-overflow recovery. Full CI/CD pipeline (Node 22/24 × Linux/macOS/Windows) and release automation (auto-tag + GitHub Release + release-time smoke test).",
-    "version": "1.34.2"
+    "version": "1.34.4"
   },
   "plugins": [
     {
       "name": "get-design-done",
       "source": "./",
       "description": "Agent-orchestrated 5-stage design pipeline: Brief → Explore → Plan → Design → Verify. 22+ specialized agents, 9 connections (Figma, Refero, Preview, Storybook, Chromatic, Figma Writer, Graphify, Pinterest, Claude Design), Claude Design handoff, bidirectional Figma write-back, and a queryable intel store (.design/intel/) for dependency and learnings queries. Standalone commands: style, darkmode, compare, figma-write, graphify, handoff, analyze-dependencies, skill-manifest, extract-learnings. Embeds NNG heuristics, WCAG thresholds, typographic systems, motion framework, and anti-pattern catalog. Ships with a full CI/CD pipeline (Node 22/24 × Linux/macOS/Windows) and release automation. Optimization layer (v1.0.4.1, retroactive): gdd-router + gdd-cache-manager skills, PreToolUse budget-enforcer hook, tier-aware agent frontmatter, lazy checker gates, streaming synthesizer, /gdd:warm-cache + /gdd:optimize commands, and cost telemetry at .design/telemetry/costs.jsonl — targeting 50-70% per-task token-cost reduction with no quality-floor regression. v1.20.0 SDK foundation: gdd-state MCP server (11 typed tools), lockfile-safe STATE.md mutations, event stream at .design/telemetry/events.jsonl, resilience primitives (jittered-backoff, rate-guard, error-classifier, iteration-budget) with rate-limit + 429 + context-overflow recovery, and TypeScript toolchain.",
-      "version": "1.34.2",
+      "version": "1.34.4",
       "author": {
         "name": "hegemonart"
       },
@@ -75,7 +75,9 @@
         "swift",
         "compose",
         "flutter",
-        "email"
+        "email",
+        "print",
+        "pdf"
       ]
     }
   ]

package/.claude-plugin/plugin.json

@@ -1,7 +1,7 @@
 {
   "name": "get-design-done",
   "short_name": "gdd",
-  "version": "1.34.2",
+  "version": "1.34.4",
   "description": "Agent-orchestrated 5-stage design pipeline: Brief → Explore → Plan → Design → Verify. 22+ specialized agents, 9 connections (Figma, Refero, Preview, Storybook, Chromatic, Figma Writer, Graphify, Pinterest, Claude Design), handoff-first workflow via Claude Design bundles, bidirectional Figma write-back (annotations, Code Connect), queryable intel store (`.design/intel/`) for O(1) design surface lookups, and self-improvement loop (reflector agent, frontmatter + budget feedback, global-skills layer at `~/.claude/gdd/global-skills/`). Standalone commands: style, darkmode, compare, figma-write, graphify, handoff, analyze-dependencies, skill-manifest, extract-learnings, reflect, apply-reflections. Embeds NNG heuristics, WCAG thresholds, typographic systems, motion framework, and anti-pattern catalog. Ships with a full CI/CD pipeline (Node 22/24 × Linux/macOS/Windows, lint + schema + frontmatter + stale-ref + shellcheck + gitleaks + injection-scan + blocking size-budget) and release automation (auto-tag + GitHub Release + release-time smoke test). Optimization layer (v1.0.4.1, retroactive): gdd-router + gdd-cache-manager skills, PreToolUse budget-enforcer hook, tier-aware agent frontmatter, lazy checker gates, streaming synthesizer, /gdd:warm-cache + /gdd:optimize commands, and cost telemetry at .design/telemetry/costs.jsonl — targeting 50-70% per-task token-cost reduction with no quality-floor regression. v1.20.0 SDK foundation: gdd-state MCP server (11 typed tools), lockfile-safe STATE.md mutations, event stream at .design/telemetry/events.jsonl, resilience primitives (jittered-backoff, rate-guard, error-classifier, iteration-budget) with rate-limit + 429 + context-overflow recovery, and TypeScript toolchain. v1.27.7 ships gdd-mcp (Phase 27.7): 12 read-only MCP tools for sub-3s priming. v1.28.0 (Phase 28): Foundational References Tier 2 — 5 new reference files (color-theory, composition, proportion-systems, i18n, contrast-advanced), 2 verifier i18n probes + 1 explore i18n-readiness probe, 12 additive cross-link insertions across 10 existing references, 2 orthogonal audit-scoring lens-tags (composition_alignment + i18n_readiness).",
   "author": {
     "name": "hegemonart",
@@ -69,7 +69,9 @@
     "swift",
     "compose",
     "flutter",
-    "email"
+    "email",
+    "print",
+    "pdf"
   ],
   "skills": [
     "./skills/"

package/CHANGELOG.md

@@ -4,6 +4,50 @@ All notable changes to get-design-done are documented here. Versions follow [sem
 
 ---
 
+## [1.34.4] - 2026-06-01
+
+### Phase 34.4 — Lazyweb + Mobbin Research Connections (recovered)
+
+Adds **two visual-reference MCP connections** to the discover stage — **Lazyweb** (free) and **Mobbin** (paid) — modeled on the existing Refero/Pinterest connection contract. Purely additive: no new pipeline stage, no new artifact, no new audit pillar; **no new runtime dependency** (both are optional user-installed MCPs, documented in their spec, never pre-declared in the plugin manifest — the Refero precedent). Recovered from a stranded Phase 30.5 fork (authored 2026-05-04 → expanded 2026-05-16) that never reached the canonical roadmap because `.planning/` is gitignored and a parallel session reused the 30.5 slot. A decimal release on the v1.34.x arc (CHANGELOG-only, D-02).
+
+### Added
+
+- **`connections/lazyweb.md` — free reference MCP (discover Tier 1, D-01).** Free bearer-token Streamable-HTTP MCP at `https://www.lazyweb.com/mcp` (`lazyweb_search` + `lazyweb_health`); 250k+ real app screens for pricing pages, onboarding flows, redesign comparisons, UI benchmarking. Copy-command setup (token at `~/.lazyweb/lazyweb_mcp_token`, then `claude plugin install lazyweb@lazyweb`) — **no auto-run** (the token write is a user-consent step). ToolSearch-only probe.
+- **`connections/mobbin.md` — curated mobile/flow reference MCP (discover Tier 2, D-01).** HTTP MCP at `https://api.mobbin.com/mcp` (`claude mcp add mobbin --transport http https://api.mobbin.com/mcp`, auto-run-safe — OAuth on first call, requires an active Mobbin subscription); 600k+ screens / 130k+ flows for mobile + flow-level references. ToolSearch-only probe.
+- **Cost-aware discover tier order (D-01).** Reference sources now resolve **Lazyweb (free, tried first) → Mobbin / Refero (paid, whichever is bound + subscribed) → Pinterest → awesome-design-md → WebFetch** — try the zero-cost source before any paid one. Wired through `connections/connections.md` (table + Capability Matrix + probe pattern, onboarded 12 → 14), `skills/discover/discover-procedure.md` (probes D/E), `skills/connections/` (`/gdd:connections` wizard + onboarding reference), and `agents/design-context-builder.md` (Area 5 rewrite + `tools` frontmatter).
+- **Regression baseline.** `test/fixtures/baselines/phase-34-4/` (onboarded-connections snapshot + `manifests-version.txt`=1.34.4) pinned by `test/suite/phase-34-4-baseline.test.cjs`.
+
+### Notes
+
+- **No new runtime dependency** — both connections are optional user-installed MCPs (Refero precedent); neither is declared in `.claude-plugin/plugin.json`. Discover-stage only — no scan/plan/design/verify integration.
+- The 31.5 tarball golden (`test/fixtures/baselines/phase-31-5/tarball-manifest.txt`) was regenerated as a reviewed delta: **+2** newly-shipped files (`connections/lazyweb.md`, `connections/mobbin.md`), zero removals. Tests are not shipped.
+- 6-manifest lockstep at **v1.34.4** (`package.json` + `package-lock.json` (root + `packages.""`) + `.claude-plugin/plugin.json` + `.claude-plugin/marketplace.json` (metadata.version + plugins[0].version) + `.cursor-plugin/plugin.json` + `.codex-plugin/plugin.json`). Version-sync hygiene upfront (D-09): `OFF_CADENCE_VERSIONS.add('1.34.4')` + the 18 live-pinned `manifests-version.txt` baselines forward-propagated 1.34.3 → 1.34.4.
+- **Provenance:** recovered from the `thirsty-curran` worktree's stranded `.planning` fork during a roadmap-reconciliation audit; the contiguity renumber (Phase 36→35 …, 2026-06-01) is unrelated and concurrent.
+
+---
+
+## [1.34.3] - 2026-05-31
+
+### Phase 34.3 — Non-Web Output Layer: Print/PDF
+
+Third and **FINAL** sub-phase of the split Phase 34 (Non-Web Output Layer) — **completing it completes the parent Phase 34** (native 34.1 + email 34.2 + print 34.3 all shipped). Adds **print/PDF output** — a dedicated executor that generates print-ready HTML/CSS honoring the real production constraints (`@page` box model, bleed + crop marks, CMYK color-space awareness, font embedding, 300dpi raster fallback) that screen-RGB web HTML ignores — behind the same project-type detector that routes native (34.1) and email (34.2). Print generation is **opt-in via project-type detection — web remains the default**. A decimal release on the v1.34.x arc (CHANGELOG-only, D-01); **no new runtime dependency** — the executor generates the print HTML/CSS as an agent-prompt and the plugin checks it with a deterministic static validator, no `pdfkit`/`paged`/`puppeteer`/`playwright` runtime (D-02/D-10). Print is the final Phase-34 output type — the project-type seam is now **closed**. 4 plans across Waves A–C.
+
+### Added
+
+- **Print-constraint catalogue + static validator (no `pdfkit`/`paged` dependency, D-02/D-03).** `reference/print-design.md` — the authoritative print-constraint catalogue (`@page` size/margin/marks — the print box model, bleed box + crop/registration marks, CMYK color-space awareness, font embedding/outlining, 300dpi raster fallback, and the on-press guidance the render-test verifies), registered in `reference/registry.json`. `scripts/lib/print/validate-print-css.cjs` — a pure, deterministic static checker (zero `require`, no fs/network/pdfkit/paged) that flags the statically-verifiable subset: `PR-PAGE-01` (an `@page` rule present), `PR-BLEED-01` (a bleed box / crop-marks signal), `PR-CMYK-01` (a CMYK-awareness signal), `PR-FONT-01` (a font-embed signal), `PR-DPI-01` (a 300dpi raster-fallback signal) — returning `{ ok, violations:[{ rule, detail }] }`.
+- **`pdf-executor` agent (Paged.js-compatible HTML/CSS + PDFKit fallback, D-02/D-04).** `agents/pdf-executor.md` — generates **print-ready output per task**: Paged.js-compatible print HTML/CSS (`@page` size/margin/marks, bleed, CMYK-aware color notes, font embedding, 300dpi raster fallback) against the `reference/print-design.md` catalogue, with PDFKit-fallback notes for Chrome-less runtimes, run through the static validator as its own self-check. It is an agent-prompt (like `design-executor`/`email-executor`), **not** a compiler — no running headless Chrome, no PDFKit, no network is required to produce the print HTML/CSS. Carries a `## Record` section from the start (the record-contract lesson) and an honest `size_budget`.
+- **`print-renderer` connection (optional render-test, degrade-to-static-validator, D-03).** `connections/print-renderer.md` — Paged.js-via-headless-Chrome (or PDFKit on Chrome-less runtimes) rendered PDF/page evidence for the verify stage when present, mirroring `connections/preview.md`. **Never hard-required**: when absent the verify stage degrades to the static print-CSS validator / code-only structural audit. Added to the `connections/connections.md` index + Capability Matrix in this closeout.
+- **`design-context-builder` `print` project-type route (seam CLOSED) + `design-verifier` consolidated non-web verify (D-06/D-07).** The context-builder appends the `print` enum + the `pdf-executor` route at the 34.1/34.2 seam and **closes the seam** — print is the final Phase-34 output type. The verifier gains the print-verify branch by **consolidating** the native + email + print non-web verify branches into ONE delegated "Non-Web Verify" section (routing by `<project_type>` to native-platforms.md / email-design.md / print-design.md + the matching validator) — a net line-reduction that keeps the verifier within its ≤700-line budget.
+- **Regression baseline.** `test/fixtures/baselines/phase-34-3/` freezes the print surface — a valid print fixture (`print-good.css`), a validator golden (`validator-golden.json`, the recorded `validatePrintCss` output for a passing + a failing fixture, proving the rule-output shape is frozen), and `manifests-version.txt`=1.34.3 — pinned by `test/suite/phase-34-3-baseline.test.cjs` so a future change cannot silently break the validator or its verdict shape.
+
+### Notes
+
+- All Phase 34.3 tests are hermetic (D-10): the static print-CSS validator is a pure string→verdict function (fixture CSS → constraint checks, no network/headless-Chrome/PDFKit), the pdf-executor is validated **structurally** (frontmatter + catalogue reference + validator reference + presence), and the default `npm test` invokes **no** headless Chrome / PDFKit and pulls in **no** `pdfkit`/`paged`/`puppeteer`/`playwright` runtime. Rendered PDF/page verification is the opt-in degraded-mode path (D-03).
+- The 31.5 tarball golden (`test/fixtures/baselines/phase-31-5/tarball-manifest.txt`) was regenerated as a reviewed delta: **+4** newly-shipped files (`agents/pdf-executor.md`, `connections/print-renderer.md`, `reference/print-design.md`, `scripts/lib/print/validate-print-css.cjs`), zero removals. Tests are not shipped.
+- 6-manifest lockstep at **v1.34.3** (`package.json` + `package-lock.json` (root + `packages.""`) + `.claude-plugin/plugin.json` + `.claude-plugin/marketplace.json` (metadata.version + plugins[0].version) + `.cursor-plugin/plugin.json` + `.codex-plugin/plugin.json`); marketplace `plugins[0].keywords` + plugin keywords gain `print`/`pdf`. Version-sync hygiene done upfront (D-09): `OFF_CADENCE_VERSIONS.add('1.34.3')` + the 17 live-pinned `manifests-version.txt` baselines forward-propagated 1.34.2 → 1.34.3 (phase-34-2, the prior closeout's own baseline, joined the set). **This completes the parent Phase 34 (Non-Web Output Layer — native + email + print).**
+
+---
+
 ## [1.34.2] - 2026-05-31
 
 ### Phase 34.2 — Non-Web Output Layer: Email

package/README.md

@@ -122,6 +122,18 @@ GDD also generates **email templates** — the project-type detector routes an `
 
 The constraints live in [`reference/email-design.md`](reference/email-design.md) — table-based layout (no flexbox/grid/`position`), inline styles (no `<style>` sheet in Gmail), MSO conditional comments for Outlook's Word engine, dark-mode `color-scheme` handling, ~600px width, and the top-20-client quirks. A deterministic static checker ([`scripts/lib/email/validate-email-html.cjs`](scripts/lib/email/validate-email-html.cjs)) flags the statically-verifiable subset (`EM-LAYOUT`/`EM-STYLE`/`EM-MSO`/`EM-DARK`). Cross-client rendered verification via [`Litmus`](connections/litmus.md) (or Email-on-Acid) is **optional** — when absent the verify stage degrades to the static validator. Email generation is opt-in; **web stays the default**.
 
+### Print/PDF output (v1.34.3)
+
+GDD also generates **print/PDF** output — the project-type detector routes a `print` brief to a dedicated executor that honors the production constraints screen-RGB web HTML ignores. This **completes the Non-Web Output Layer** (native + email + print all shipped):
+
+- **[`pdf-executor`](agents/pdf-executor.md)** — generates **Paged.js-compatible print HTML/CSS** (with PDFKit-fallback notes for Chrome-less runtimes) against the constraint catalogue, with the static validator as its own self-check. It is an agent-prompt, not a compiler — **no headless Chrome, no PDFKit, no network** is needed to produce the print HTML/CSS.
+
+The constraints live in [`reference/print-design.md`](reference/print-design.md) — the `@page` box model (size/margin/marks), bleed box + crop/registration marks, CMYK color-space awareness (print is subtractive CMYK, not screen RGB), font embedding/outlining (print RIPs have no web fonts), and a 300dpi raster fallback. A deterministic static checker ([`scripts/lib/print/validate-print-css.cjs`](scripts/lib/print/validate-print-css.cjs)) flags the statically-verifiable subset (`PR-PAGE`/`PR-BLEED`/`PR-CMYK`/`PR-FONT`/`PR-DPI`). Rendered PDF/page verification via the optional [`print-renderer`](connections/print-renderer.md) connection (Paged.js/headless-Chrome or PDFKit) is **optional** — when absent the verify stage degrades to the static validator. Print generation is opt-in; **web stays the default**.
+
+### Research connections — Lazyweb + Mobbin (v1.34.4)
+
+The **discover** stage grounds design in real product references, resolving sources **cost-aware — the free source is tried before any paid one**. [`Lazyweb`](connections/lazyweb.md) (free MCP, 250k+ app screens — pricing pages, onboarding, redesign comparisons) is **Tier 1, always first**; [`Mobbin`](connections/mobbin.md) (paid MCP, 600k+ screens / 130k+ flows — mobile + flow-level) and [`Refero`](connections/refero.md) are **Tier 2** (use whichever you subscribe to), then Pinterest → local archetypes → WebFetch. Both are optional user-installed MCPs (**no new runtime dependency**), onboardable via `/gdd:connections`.
+
 ### Previous releases
 
 - **v1.26.0** — Headless Model Resolver (per-runtime tier→model map, `resolved_models` router field, per-runtime price tables, `reasoning-class` runtime-neutral alias).

package/agents/design-context-builder.md

@@ -1,7 +1,7 @@
 ---
 name: design-context-builder
 description: Detects existing design system state via grep/glob, runs discovery interview asking ONLY unanswered questions, produces .design/DESIGN-CONTEXT.md. Spawned by the discover stage.
-tools: Read, Write, Bash, Grep, Glob, mcp__figma__get_variable_defs, mcp__figma__get_metadata, mcp__figma-desktop__get_variable_defs, mcp__figma-desktop__get_metadata, mcp__Figma__get_variable_defs, mcp__Figma__get_metadata, mcp__refero__search
+tools: Read, Write, Bash, Grep, Glob, mcp__figma__get_variable_defs, mcp__figma__get_metadata, mcp__figma-desktop__get_variable_defs, mcp__figma-desktop__get_metadata, mcp__Figma__get_variable_defs, mcp__Figma__get_metadata, mcp__refero__search, mcp__lazyweb__search, mcp__lazyweb__health, mcp__mobbin__search
 required_reading:
   - connections/storybook.md
 color: blue
@@ -218,19 +218,20 @@ Proceed to Step 0E regardless of whether Step 0D ran or was skipped.
 
 Detect the **project type** so the pipeline routes the brief to the correct executor. Reuse the Step 0C / Step 1 grep/glob idiom (file reads only, < 1 second, no skip condition).
 
-**Enum (5 values — D-06):** `web` (DEFAULT) · `native-ios` · `native-android` · `flutter` · `email`.
+**Enum (6 values — D-06, the full set):** `web` (DEFAULT) · `native-ios` · `native-android` · `flutter` · `email` · `print`.
 
-**Detection signals + precedence** (first match wins; brief overrides — if the user explicitly says "iOS app" / "Android app" / "Flutter app" / "email" / "newsletter" / "email template", honor that):
+**Detection signals + precedence** (first match wins; brief overrides — if the user explicitly says "iOS app" / "Android app" / "Flutter app" / "email" / "newsletter" / "email template" / "print" / "PDF" / "print-ready" / "brochure" / "flyer" / "poster", honor that):
 
 ```bash
 ls pubspec.yaml 2>/dev/null                       # → flutter
 ls *.xcodeproj Package.swift 2>/dev/null          # → native-ios   (when no pubspec)
 ls build.gradle build.gradle.kts settings.gradle 2>/dev/null  # → native-android (when no pubspec)
 ls **/*.mjml email/ emails/ templates/email 2>/dev/null  # → email (email-template signals)
+ls **/*.print.css print/ templates/print 2>/dev/null  # → print (print-output signals: a print stylesheet / print-template dir)
 ls package.json 2>/dev/null                       # → web          (default; also the fallback when none match)
 ```
 
-Precedence: an explicit brief override (the user says "email" / "newsletter" / "email template") wins like the other brief-overrides; otherwise `pubspec.yaml` (flutter) > `*.xcodeproj`/`Package.swift` (native-ios) > `build.gradle*`/`settings.gradle` (native-android) > `.mjml` files / an `email/` templates directory (email) > `package.json` / none (web — DEFAULT).
+Precedence: an explicit brief override (the user says "email" / "newsletter" / "email template", or "print" / "PDF" / "print-ready" / "brochure" / "flyer" / "poster") wins like the other brief-overrides; otherwise `pubspec.yaml` (flutter) > `*.xcodeproj`/`Package.swift` (native-ios) > `build.gradle*`/`settings.gradle` (native-android) > `.mjml` files / an `email/` templates directory (email) > a print stylesheet (`*.print.css`) / a `print/` templates directory (print) > `package.json` / none (web — DEFAULT).
 
 **Routing table** (project type → executor — one row per type, trivially appendable):
 
@@ -241,10 +242,11 @@ Precedence: an explicit brief override (the user says "email" / "newsletter" / "
 | native-android   | compose-executor  |
 | flutter          | flutter-executor  |
 | email            | email-executor    |
+| print            | pdf-executor      |
 
-<!-- 34.2 added `email` (above) → email-executor; 34.3 (print) appends its project type + executor row HERE — this enum and routing table stay intentionally OPEN and extensible (D-06). 34.2 adds email ONLY; do NOT add a print row until 34.3. -->
+<!-- Phase 34 output types complete: native (34.1: native-ios/native-android/flutter) + email (34.2) + print (34.3). Print is the FINAL Phase-34 output type — no further Phase-34 output types; the enum + routing table above are the full set. (34.1/34.2 kept this seam OPEN for the next type; 34.3 ties it off.) -->
 
-Record the detected type in DESIGN-CONTEXT.md as a `<project_type>` line (e.g. `<project_type>native-ios</project_type>`) so downstream stages route correctly. The native specifics (token→theme bridge) live in `reference/native-platforms.md`; the email specifics (table layout, inline styles, MSO/dark-mode constraints) live in `reference/email-design.md` — do not inline either here.
+Record the detected type in DESIGN-CONTEXT.md as a `<project_type>` line (e.g. `<project_type>native-ios</project_type>`) so downstream stages route correctly. The native specifics (token→theme bridge) live in `reference/native-platforms.md`; the email specifics (table layout, inline styles, MSO/dark-mode constraints) live in `reference/email-design.md`; the print specifics (the `@page` box model, bleed/crop marks, CMYK awareness, font embedding, 300dpi raster) live in `reference/print-design.md` — do not inline any of them here.
 
 Proceed to Step 1 regardless of outcome.
 
@@ -381,51 +383,34 @@ The NOT is equally important:
 
 **Style direction (style-vocabulary.md):** Ask the user to confirm or adjust the inferred UI aesthetic style before writing the context file. Infer the style from the brand direction words captured above. Look up the inferred style name verbatim in `reference/style-vocabulary.md` to confirm it is coherent with the product type (Best For / Avoid For columns) and to surface the performance cost (Performance column) in the Constraints section. Record the confirmed style name verbatim in the context file as a `D-0N` decision so downstream agents can pattern-match it. Example: `D-04: [Style] "Glassmorphism Dark" — confirmed for gaming media player context; GPU cost noted in constraints.`
 
-### Area 5 — Visual References (Refero-augmented)
+### Area 5 — Visual References (cost-aware — free source first)
 
-This area uses Refero MCP when available, with graceful fallback to local brand archetypes and finally WebFetch. Refero tool names may vary — verify via ToolSearch before calling.
+This area pulls real product references, resolving sources **cost-aware (D-01, Phase 34.4): try the free source before any paid one.** Check `.design/STATE.md` `<connections>` for `lazyweb:` / `mobbin:` / `refero:` / `pinterest:` status before proceeding. Tool names may vary — verify via ToolSearch before calling. **Two or more references are required.**
 
-Check `.design/STATE.md` `<connections>` for `refero:` status before proceeding.
+**Tier 1 — Lazyweb (FREE — tried first; if `lazyweb: available`)**
 
-**Tier 1 — Refero (if `refero: available` in `.design/STATE.md` `<connections>`)**
-
-ToolSearch first — Refero tools may be in the deferred tool set:
+ToolSearch first (tools may be deferred): `ToolSearch({ query: "lazyweb", max_results: 10 })` (expect `lazyweb_search` + `lazyweb_health`). Run ≥2 `lazyweb_search` queries — one **structural** (from README/scope, e.g. `"pricing page three tiers"`, `"onboarding checklist"`, `"data table pagination"`) + one **aesthetic** (from the Area-4 brand direction, e.g. `"warm editorial SaaS"`, `"neutral Swiss dashboard"`). Pre-populate:
 
 ```
-ToolSearch({ query: "refero", max_results: 10 })
+L-01: [Lazyweb result title] — source: lazyweb — borrow: [inferred borrow rationale]
+L-02: [Lazyweb result title] — source: lazyweb — borrow: [inferred borrow rationale]
 ```
 
-Confirm the exact search tool name from results (expected: `mcp__refero__search` — may differ).
-
-Run at least 2 searches:
-
-1. **Structural query** — inferred from README / project scope (example: `"admin dashboard filters"`, `"onboarding flow"`, `"data table pagination"`)
-2. **Aesthetic query** — inferred from brand direction captured in Area 4, if any (example: `"brutalist editorial UI"`, `"warm developer tool dashboard"`)
-
-Select 2–3 results. Pre-populate references as:
-
-```
-R-01: [Refero result title] — source: refero — borrow: [inferred borrow rationale from result content]
-R-02: [Refero result title] — source: refero — borrow: [inferred borrow rationale]
-```
-
-Present to user: "I found these references from Refero. Confirm or replace?"
-
-**Tier 2 — awesome-design-md (if `refero: not_configured` OR `refero: unavailable`)**
+**Tier 2 — Mobbin / Refero (PAID — use whichever is bound + has an active subscription; if both, Mobbin for mobile/flow-level, Refero for broad screen-level)**
 
-Look in `~/.claude/libs/awesome-design-md/design-md/` — 68 brand archetypes, each with a full `DESIGN.md` token file. Pick 1–2 closest matches by inferred product category (e.g., B2B SaaS → Linear, Vercel; consumer → Airbnb, Spotify; editorial → NYT, Bloomberg).
+Fall here when Lazyweb is unavailable, or for paid depth. If `mobbin: available`: `ToolSearch({ query: "mobbin", max_results: 10 })`, run structural/flow + aesthetic queries, cite `M-01: [title] — source: mobbin — borrow: …`. If `refero: available`: `ToolSearch({ query: "refero", max_results: 10 })` (expected `mcp__refero__search` — may differ), run a structural + an aesthetic query, cite `R-01: [title] — source: refero — borrow: …`. Present to user: "I found these references. Confirm or replace?"
 
-Pre-populate: `R-01: [Brand name] — source: awesome-design-md — borrow: [token values — color palette, spacing scale, typography]`
+**Tier 3 — Pinterest (if `pinterest: available`)**
 
-Add a note in `<references>`: `Note: Refero unavailable — using local brand archetypes as references.`
+Visual inspiration search via the verified Pinterest tool (ToolSearch `"mcp-pinterest"` first). Cite `P-01: [title] — source: pinterest — borrow: …`.
 
-**Tier 3 — WebFetch (last resort, if awesome-design-md unavailable)**
+**Tier 4 — awesome-design-md (local brand archetypes, if no reference MCP is available)**
 
-Ask the user for a getdesign.md URL. WebFetch it and extract design tokens.
+Look in `~/.claude/libs/awesome-design-md/design-md/` — 68 brand archetypes, each with a full `DESIGN.md` token file. Pick 1–2 closest matches by inferred product category (e.g., B2B SaaS → Linear, Vercel; consumer → Airbnb, Spotify; editorial → NYT, Bloomberg). Pre-populate `R-01: [Brand name] — source: awesome-design-md — borrow: [token values — color palette, spacing scale, typography]` + add a note in `<references>`: `Note: no reference MCP available — using local brand archetypes.`
 
-Pre-populate: `R-01: [URL] — source: webfetch — borrow: [extracted tokens: color palette, type scale, spacing units]`
+**Tier 5 — WebFetch (last resort, if awesome-design-md unavailable)**
 
-Note: Refero tool name may differ — always verify via ToolSearch. Two or more references are required.
+Ask the user for a getdesign.md URL. WebFetch it and extract design tokens. Pre-populate `R-01: [URL] — source: webfetch — borrow: [extracted tokens: color palette, type scale, spacing units]`.
 
 ### Area 6 — Constraints
 

package/agents/design-verifier.md

@@ -354,21 +354,17 @@ In DESIGN-VERIFICATION.md, add a `## Phase 4B — Screenshot Evidence` section l
 
 ---
 
-## Phase 4D — Native Verify (no-DOM targets)
+## Phase 4D — Non-Web Verify (no-DOM targets)
 
-When `<project_type>` in DESIGN-CONTEXT.md is `native-ios` / `native-android` / `flutter` (no browser DOM), the Phase-1 DOM grep audit + the Phase-4B Preview loop do not apply as-is. Run instead:
+When `<project_type>` is a **no-DOM target** — `native-ios`/`native-android`/`flutter`, `email`, or `print` — the Phase-1 web DOM grep + the Phase-4B Preview loop do not apply as-is. Route by `<project_type>` to the matching constraint/structural audit **by delegation** (the per-type rules live in the reference, never inlined here), with the optional render-connection as a degrade-able enhancement — the Phase-4B precedent:
 
-- **Snapshot audit** — IF a simulator/emulator screenshot is supplied (via `connections/xcode-simulator.md`, `connections/android-emulator.md`, or Preview for Flutter-web — all OPTIONAL): reuse the Phase-4B screenshot-evidence machinery against the supplied image.
-- **Code-only structural audit** (DEFAULT — no screenshot/simulator): verify the generated native source structurally — expected SwiftUI views / Compose composables / Flutter widgets present + token-bridge usage — instead of rendered pixels. What "structurally valid" means per platform lives in `reference/native-platforms.md` (do not inline it). Like Phase 4B, the simulator/emulator is an **enhancement, not a requirement** — this branch NEVER hard-requires one; it degrades to the code-only audit and raises no blocker unless a must_have explicitly demands rendered evidence.
-
----
-
-## Phase 4E — Email Verify (project_type: email)
-
-When `<project_type>` is `email` (no browser DOM — the Phase-1 DOM grep + Phase-4B Preview loop do not apply), run an email-constraint audit BY DELEGATION (the ~30 constraints live in `reference/email-design.md` — the authority; do NOT inline them):
+| `<project_type>` | reference (authority) + static audit | optional render-connection (degrade if absent) |
+|---|---|---|
+| `native-ios` / `native-android` / `flutter` | `reference/native-platforms.md` — **code-only structural audit**: expected SwiftUI views / Compose composables / Flutter widgets present + token-bridge usage (a snapshot audit when a screenshot is supplied) | `xcode-simulator` / `android-emulator` / Preview (Flutter-web) → degrade to the code-only structural audit |
+| `email` | `reference/email-design.md` + `scripts/lib/email/validate-email-html.cjs` (`validateEmailHtml`) over the generated HTML — table layout / inline styles / MSO comments / dark-mode `color-scheme` | `connections/litmus.md` cross-client screenshots → degrade to the static validator / code-only |
+| `print` | `reference/print-design.md` + `scripts/lib/print/validate-print-css.cjs` (`validatePrintCss`) over the print CSS/HTML — `@page` box, bleed/crop marks, CMYK awareness, font embedding, 300dpi | `connections/print-renderer.md` (Paged.js-headless / PDFKit render) → degrade to the static validator / code-only |
 
-- **Static constraint audit** (DEFAULT) — run `scripts/lib/email/validate-email-html.cjs` (`validateEmailHtml`) over the generated email HTML and report its violations (table layout / inline styles / MSO conditional comments / dark-mode `color-scheme`).
-- **Rendered enhancement** (OPTIONAL) — IF the Litmus connection (`connections/litmus.md`) is available, reuse the Phase-4B screenshot-evidence machinery against its cross-client screenshots; when absent, DEGRADE to the static validator / code-only. Litmus is an **enhancement, never hard-required** (D-03 — the Phase-4D precedent); raise no blocker for its absence.
+**Degrade posture (D-03, the Phase-4B precedent — applies to every row):** the render-connection (simulator/emulator/Litmus/print-render) is an **enhancement, NEVER hard-required**. When it is absent, run the default code-only/static audit for that type and raise **no blocker** for the missing render — unless a must_have explicitly demands rendered evidence. Each reference owns its own constraint detail; this section is a pure router.
 
 ---
 

package/agents/pdf-executor.md

@@ -0,0 +1,144 @@
+---
+name: pdf-executor
+description: Executes one plan task by generating print-ready output — Paged.js-compatible print HTML/CSS (@page/bleed/CMYK-aware/font-embed/300dpi) with PDFKit-fallback notes — honoring reference/print-design.md constraints, validated by the static print-CSS checker. Single-shot; mirrors design-executor.
+tools: Read, Write, Edit, Bash, Grep, Glob
+color: pink
+default-tier: sonnet
+tier-rationale: "Follows an Opus-authored plan; executes print codegen rather than plans it"
+size_budget: M
+size_budget_rationale: "Honest tier sized to the actual ~150-line body (M cap 300), NOT inflated to the design-family XXL default. Print carries a single-artifact generation contract (Paged.js-compatible print HTML/CSS, D-02) plus a five-class static-validator self-check (PR-PAGE/BLEED/CMYK/FONT/DPI) and an optional render-test posture — comparable to the email-executor (also M) for a single-target lean executor body. The @page box model, 3mm-bleed/crop-mark, rich-black-vs-K100, font-embed, and 300dpi per-press/per-RIP detail is DELEGATED to reference/print-design.md (the catalogue), keeping the body well under M; only the generation + validation + degrade contract is stated here. Raise to LARGE only if the per-press surface is ever inlined here instead of the catalogue."
+parallel-safe: conditional-on-touches
+typical-duration-seconds: 60
+reads-only: false
+writes:
+  - "**/*.html"
+  - "**/*.css"
+---
+
+@reference/shared-preamble.md
+
+# pdf-executor
+
+## Role
+
+You execute **exactly one task** from the plan: you generate **one print-ready document** — **Paged.js-compatible print HTML/CSS** (the `@page` box model, bleed, CMYK-aware color, embedded fonts, a 300dpi raster fallback) — honoring the print-production constraints. Your scope is a single task — you do not re-plan, coordinate waves, spawn other agents, or ask clarifying questions. The stage handles dispatch; you handle one task completely and correctly.
+
+You are a single-shot agent: receive context, read the references, generate the print HTML/CSS, write the file(s), run the static validator, commit, emit the completion marker, done.
+
+You are an **agent-prompt**, not a compiler (D-04): GDD generates the print document when an LLM (you) invokes this prompt, consistent with `design-executor.md` / `email-executor.md` / `flutter-executor.md`. You do **not** require a running headless Chrome, a Paged.js runtime, PDFKit, or any network to produce the print HTML/CSS — rendered PDF verification is the verify stage's degraded-mode concern, never a precondition here (D-03/D-10).
+
+---
+
+## Required Reading
+
+Read every file the stage lists in its `<required_reading>` block before taking any action. At minimum:
+
+- `.design/STATE.md` — pipeline state (decisions, blockers, must-haves)
+- `.design/DESIGN-PLAN.md` — your task is identified by `task_id`
+- `.design/DESIGN-CONTEXT.md` — brand decisions, constraints, locked choices
+- **`reference/print-design.md`** — the **authoritative** print-constraint catalogue: the `@page` box model (`size`/`margin`/`marks`), the bleed box + crop/registration marks (~3mm), CMYK awareness (subtractive ink, not screen RGB), font embedding (RIPs have no web fonts — `@font-face` with an embedded `src:` or outline-to-vector), and the 300dpi raster fallback (`image-resolution`/`min-resolution`). This is how you pick the correct print idiom — you **generate against the catalogue**, you do **not** re-derive these rules (the `email-executor`→`reference/email-design.md`, `flutter-executor`→`reference/native-platforms.md` precedent).
+
+**Invariant:** read all listed files FIRST, before making any changes.
+
+---
+
+## Paged.js-compatible print HTML/CSS + PDFKit fallback (the D-02 generation contract)
+
+Per **D-02** the executor's canonical output is **Paged.js-compatible print HTML/CSS**, and **you (the LLM) perform the generation as your contract** — there is **NO `pdfkit`/`paged`/`puppeteer`/`playwright` build step / runtime dependency** (an opt-in real Paged.js-via-headless-Chrome / PDFKit render is out of scope, like the simulator/Litmus connections):
+
+- Generate a **Paged.js-compatible print stylesheet** as the canonical artifact: an `@page` rule (`size` A4/Letter or explicit physical `WIDTH HEIGHT`, `margin`, `marks: crop cross`), a `bleed:` declaration (~3mm), CMYK-aware color (a `cmyk()` value, an ICC `color-profile` reference, or an explicit CMYK-target note), `@font-face` font embedding (embedded `src:`), and a 300dpi raster fallback (`image-resolution: 300dpi`/`from-image` or a documented note) — per the catalogue.
+- Document a **PDFKit-fallback construction path** for **Chrome-less runtimes** — a note on how PDFKit would build the same page box (`new PDFDocument({ size, margins })`), embed fonts (`doc.registerFont(...)`), and place the bleed when Paged.js-via-headless-Chrome is unavailable. This is documentation, not a dependency.
+- State, in the file header comment and your output, that the **print HTML/CSS is the canonical artifact** and a **rendered PDF is the optional print-render connection's product** — never produced by a bundled build step.
+- Do **not** add `pdfkit`/`paged`/`puppeteer`/`playwright` to `package.json` or shell out to them — the generation is your job.
+
+---
+
+## Token Consumption — the canonical token form
+
+Where the task themes the document (colors, spacing, type), consume the **canonical design tokens** (the css-vars token form) for those values rather than inventing ad-hoc hex/px — consistent with the design-family executors. Print is **subtractive CMYK**, so **resolve** the token color to a **print-safe literal** at generation time and **note CMYK awareness** (the token is the RGB source; the print output carries the CMYK-aware resolved value + the production-intent note per the catalogue). Prefer physical units (`mm`/`pt`) for page geometry. Keep color, type scale, and brand voice consistent with the rest of the design system.
+
+---
+
+## Self-check via the static validator (the deterministic gate)
+
+Before completing, **run the static print-CSS validator** on your **generated print CSS/HTML**:
+
+```js
+const { validatePrintCss } = require('scripts/lib/print/validate-print-css.cjs');
+const { ok, violations } = validatePrintCss(cssOrHtmlString);
+```
+
+`validatePrintCss` (Phase 34.3-01) deterministically checks the five statically-verifiable constraint classes — **PR-PAGE-01** (an `@page` rule present), **PR-BLEED-01** (a `bleed:`/`marks:` or documented crop-marks signal), **PR-CMYK-01** (a `cmyk()`/`color-profile`/CMYK-note signal), **PR-FONT-01** (an `@font-face` `src:` or font-embed/outline note), **PR-DPI-01** (an `image-resolution`/`min-resolution`/300dpi note). **Fix every flagged violation** before you finish — this is your deterministic self-check against the catalogue. The remaining catalogue rules (3mm bleed value, rich-black vs K100, overprint/knockout, trap/registration, true vector tessellation, effective ≥300dpi) are render-tested guidance, not statically asserted — honor them from the catalogue.
+
+---
+
+## Optional print-render (degraded / not a precondition)
+
+Code generation needs **no** render service (D-04/D-10). Rendered **PDF/page-proof** verification is the **verify stage's** degraded-mode concern (D-03): point it at the `connections/print-renderer.md` print-render connection **as an enhancement**, **never** a precondition.
+
+- When the **print-render** (Paged.js via headless Chrome, or **PDFKit** for Chrome-less runtimes) is available → the verify stage captures a paginated PDF/page proof.
+- When **absent** → verification **degrades** to the static validator above, then a code-only structural audit. Never hard-require the print-render.
+
+Print ships its render-test connection at `connections/print-renderer.md`; you only **name** it — you never run it to generate.
+
+---
+
+## Execution Principles
+
+1. **Honor DESIGN-CONTEXT.md decisions as locked.** `D-XX:` decisions are non-negotiable.
+2. **`reference/print-design.md` is authoritative** for the print constraints. Apply its rules directly; do not paste them wholesale and do not re-derive them.
+3. **Observable outcomes only.** Acceptance criteria describe observable states ("the CSS declares an `@page` rule with `marks: crop`", "an `@font-face` with an embedded `src:` is present", "validatePrintCss returns `ok: true`").
+4. **Decision authority:** in-context choices → proceed; out-of-context (architectural, contradicts a locked D-XX, changes external API) → Rule 4: STOP, write a blocker, mark the task `status: deviation`, still emit the marker.
+5. **Single-task scope.** Do not modify the plan, the context file, the connection index, or any file outside the task's `Touches:`/`writes` list (unless a deviation fix requires it — document it).
+
+---
+
+## Deviation Rules
+
+Apply automatically; track each in the task output `## Deviations` section.
+
+- **Rule 1 — Bug:** broken print HTML/CSS, a flagged `validatePrintCss` violation, wrong token resolution in files you author → fix inline.
+- **Rule 2 — Missing Critical:** a missing `@page` rule, no bleed/crop-marks signal, pure screen-RGB with no CMYK awareness, a bare system-font-stack with no embed, no 300dpi signal → add it (the catalogue requires it).
+- **Rule 3 — Blocking:** a referenced file/import missing, the validator not resolvable → fix (resolve import, create stub) and note it.
+- **Rule 4 — Architectural:** switching the print engine, restructuring the document system, a schema-level change, or anything contradicting a locked D-XX → STOP, write a `<blocker>`, mark `status: deviation`, still emit the marker.
+
+**Scope boundary:** only fix issues directly caused by this task's changes. **Fix attempt limit:** stop after 3 attempts on one issue; document the remainder and continue to commit.
+
+---
+
+## Output
+
+Emit the **Paged.js-compatible print HTML/CSS** to the path(s) the task declares. In your final response, state: the file(s) written, the page geometry chosen (`@page size`/`margin`/`bleed`/`marks`), how tokens were resolved to print-safe CMYK-aware values, the PDFKit-fallback note, and the `validatePrintCss` result (`ok: true` / the violations you fixed). Write the task record per the design-family output contract and make an atomic commit (stage files individually — never `git add .`/`-A`; never run `git clean`).
+
+Terminate with exactly this line, on its own line:
+
+```
+## EXECUTION COMPLETE
+```
+
+---
+
+## Constraints
+
+This agent MUST NOT:
+
+- Run `git clean` (any flags) — absolute prohibition.
+- Require a running headless Chrome, a Paged.js runtime, PDFKit, or any network to generate the print HTML/CSS (D-04/D-10).
+- Add a `pdfkit`/`paged`/`puppeteer`/`playwright` dependency to `package.json` or shell out to them — the generation is the agent's contract (D-02).
+- Re-derive the print constraints — consume `reference/print-design.md` (the catalogue).
+- Emit screen-only RGB HTML with no `@page`/bleed/CMYK/font-embed/300dpi print semantics — the print contract is the deliverable.
+- Create or edit the connection index, or modify the plan or context file, re-plan, spawn other agents, ask clarifying questions, or `git add .`/`-A`.
+
+---
+
+## Record
+
+At run-end, append one JSONL line to `.design/intel/insights.jsonl`:
+
+```json
+{"ts":"<ISO-8601>","agent":"pdf-executor","cycle":"<cycle from STATE.md>","stage":"<stage from STATE.md>","one_line_insight":"<which print document (Paged.js-compatible HTML/CSS) was generated + the validatePrintCss result>","artifacts_written":["<files written>"]}
+```
+
+Schema: `reference/schemas/insight-line.schema.json`.
+
+## EXECUTION COMPLETE

package/connections/connections.md

@@ -2,7 +2,7 @@
 
 This directory contains connection specifications for external tools and MCPs that the get-design-done pipeline integrates with. Each connection has its own spec file. This file is the index.
 
-**Getting started:** run `/gdd:connections` for the interactive onboarding wizard — it probes all 12 connections, recommends setup based on your project type, and walks you through installing each one (auto-run for reversible MCP adds, copy-command for everything else). You can also run `/gdd:connections list` for a read-only status check or `/gdd:connections <name>` to jump to a single connection's setup.
+**Getting started:** run `/gdd:connections` for the interactive onboarding wizard — it probes all 14 connections, recommends setup based on your project type, and walks you through installing each one (auto-run for reversible MCP adds, copy-command for everything else). You can also run `/gdd:connections list` for a read-only status check or `/gdd:connections <name>` to jump to a single connection's setup.
 
 ---
 
@@ -27,6 +27,9 @@ This directory contains connection specifications for external tools and MCPs th
 | Xcode Simulator | Active | [`connections/xcode-simulator.md`](connections/xcode-simulator.md) | **Optional** (macOS-only); CLI: `simctl` (no MCP); native-iOS rendered evidence for verify; degrade-to-code-only when absent (D-03) |
 | Android Emulator | Active | [`connections/android-emulator.md`](connections/android-emulator.md) | **Optional**; CLI: `adb` / `emulator` (no MCP); native-Android rendered evidence for verify; degrade-to-code-only when absent (D-03) |
 | Litmus | Active | [`connections/litmus.md`](connections/litmus.md) | **Optional** render-test (email; Email-on-Acid alternative); cross-client rendered screenshots for verify; degrade-to-static-validator / code-only when absent (D-03) |
+| Print-Renderer | Active | [`connections/print-renderer.md`](connections/print-renderer.md) | **Optional** print render-test (Paged.js/headless-Chrome or PDFKit); rendered PDF/page proof for verify; degrade-to-static-validator (validate-print-css.cjs) / code-only when absent (D-03) |
+| Lazyweb | Active | [`connections/lazyweb.md`](connections/lazyweb.md) | **Free** bearer-token MCP `lazyweb_search` / `lazyweb_health` (ToolSearch-only probe; copy-command setup, no auto-run); discover **Tier 1** — tried first (D-01) |
+| Mobbin | Active | [`connections/mobbin.md`](connections/mobbin.md) | **Paid** HTTP MCP `claude mcp add mobbin --transport http https://api.mobbin.com/mcp` (ToolSearch-only probe; auto-run-safe, OAuth); discover **Tier 2** — mobile/flow-level (D-01) |
 
 ---
 
@@ -53,6 +56,9 @@ Each cell describes what the connection contributes at that pipeline stage, or `
 | Xcode Simulator | — | — | — | native iOS code-gen target (swift-executor / emitSwift) | rendered SwiftUI snapshot when simulator available, else degrade to code-only structural audit (D-03) | — | — |
 | Android Emulator | — | — | — | native Android code-gen target (compose-executor / emitCompose) | rendered Compose screenshot when emulator available, else degrade to code-only structural audit (D-03) | — | — |
 | Litmus | — | — | — | email render-test target (email-executor) | cross-client rendered evidence when Litmus available, else degrade to the static email-HTML validator / code-only (D-03) | — | — |
+| Print-Renderer | — | — | — | print render-test target (pdf-executor) | rendered PDF/page evidence when the print-render is available, else degrade to the static print-CSS validator / code-only (D-03) | — | — |
+| Lazyweb | — | reference search via `lazyweb_search` (**Tier 1 — free, tried first**; D-01); complements refero/pinterest | — | — | — | — | — |
+| Mobbin | — | reference search via mobbin tools (**Tier 2 — paid, mobile/flow-level**; D-01); complements refero/lazyweb | — | — | — | — | — |
 
 **Column definitions:**
 
@@ -136,6 +142,30 @@ Write refero status to STATE.md <connections>.
 
 Note: Refero probe is ToolSearch-only (no live tool call). ToolSearch presence is sufficient; a live Refero search as probe would waste tokens before confirming the connection is even needed.
 
+**Lazyweb probe (execute at stage entry, after reading STATE.md):**
+
+```
+Step D1 — ToolSearch check:
+  ToolSearch({ query: "lazyweb", max_results: 5 })
+  → Empty result      → lazyweb: not_configured  (use fallback chain)
+  → Non-empty result  → lazyweb: available
+
+Write lazyweb status to STATE.md <connections>.
+```
+
+**Mobbin probe (execute at stage entry, after reading STATE.md):**
+
+```
+Step E1 — ToolSearch check:
+  ToolSearch({ query: "mobbin", max_results: 5 })
+  → Empty result      → mobbin: not_configured  (use fallback chain)
+  → Non-empty result  → mobbin: available
+
+Write mobbin status to STATE.md <connections>.
+```
+
+Note: Lazyweb + Mobbin probes are ToolSearch-only (no live call). The discover stage resolves reference sources **cost-aware (D-01): Lazyweb (free) → Mobbin / Refero (paid, whichever is bound + subscribed) → Pinterest → awesome-design-md → WebFetch.**
+
 ---
 
 **Preview probe (execute at stage entry, after reading STATE.md):**