{"id":98820,"plugin_id":"plugin_asdk_app_6ad699a529a881919b04b3bd0511ecb4","kind":"skill","collection_source":"plugin_package","comparison_source":null,"observed_at":"2026-11-16T18:15:42.897Z","digest":"dbd0b4f2e62eacc7d68a43703c60c57dcab469ddf925fb0fb14cb91975d6d561","against":null,"payload":{"description":"Produce a short PDF — one page whenever the content fits — that an administrator forwards to their END\nUSERS, telling those users what systems an existing Dtwo gateway reaches and how to connect their own AI\nclient to it. Tailored to one client (Claude\nCode, Claude Desktop, Cursor, Codex) and to whether the organization has already configured that client\ncentrally. This documents a gateway for the people who will use it — it does not build or change one.\nTRIGGER when: user wants something to hand to their users — \"a guide I can send the team\", \"instructions for\nmy users\", \"how do people connect to this\", an end-user one-pager, handout, or rollout doc for a gateway.\nSKIP when: the user is creating, configuring or deploying a gateway themselves (use setup for a first\ngateway, dtwo-gateway-config for YAML and MCP server entries); attaching or publishing policies (use\ndtwo-gateway-policy); writing Rego (use dtwo-policy-rego).\n","included_files":[],"name":"dtwo-end-user-guide","skill_md_contents":"---\nname: dtwo-end-user-guide\ndescription: |\n  Produce a short PDF — one page whenever the content fits — that an administrator forwards to their END\n  USERS, telling those users what systems an existing Dtwo gateway reaches and how to connect their own AI\n  client to it. Tailored to one client (Claude\n  Code, Claude Desktop, Cursor, Codex) and to whether the organization has already configured that client\n  centrally. This documents a gateway for the people who will use it — it does not build or change one.\n  TRIGGER when: user wants something to hand to their users — \"a guide I can send the team\", \"instructions for\n  my users\", \"how do people connect to this\", an end-user one-pager, handout, or rollout doc for a gateway.\n  SKIP when: the user is creating, configuring or deploying a gateway themselves (use setup for a first\n  gateway, dtwo-gateway-config for YAML and MCP server entries); attaching or publishing policies (use\n  dtwo-gateway-policy); writing Rego (use dtwo-policy-rego).\n---\n\n<!-- © 2026 Dtwo, Inc. -->\n\n# Dtwo End-User Guide\n\nYou produce a short PDF an administrator forwards to their colleagues — one page when the content fits, two\nwhen the gateway is large. It tells those colleagues what\nsystems their AI assistant can now reach through an existing Dtwo gateway, and exactly how to connect their\nown client to it.\n\n**The reader is not the administrator.** The person running this skill already has a gateway; the person\nholding the output is someone who just needs to use it. Write for a non-technical colleague who has never\nheard of MCP. Nothing in the document tells anyone how to create or configure a gateway.\n\n## Companion skills\n\n- **dtwo-gateway-config** — load when the user wants to change what's behind the gateway before documenting it.\n- **setup** — the admin-facing counterpart. If the user has no gateway yet, they want that skill, not this one.\n\n## Voice\n\n- Plain and direct. No marketing language, no superlatives, no \"unlock\", \"seamless\", \"empower\".\n- **Never call Dtwo a \"gateway\" in the document.** That word is internal. To end users it is a connection, or just Dtwo.\n- Value first, mechanism second. Say what the reader can now do, not how routing works.\n- Short sentences. Contractions are fine.\n\n## Step 1 — Pick the gateway\n\nCall `dtwo-list-gateways`. Show the user the gateways by name and ask which one the document is for.\n\nIf the Dtwo MCP server is not connected, say so and stop — the document cannot be built without the gateway's\nreal server list. Never invent connected systems.\n\n## Step 2 — Read the gateway configuration\n\nFrom the chosen gateway's `configuration` YAML, extract:\n\n- `url` — the MCP endpoint users connect to.\n- `mcp_servers[].name` — the connected systems. These drive the whole first section.\n- The auth mode, which decides the sign-in wording:\n  - `jwks_info.jwt_issuer` is a Dtwo Auth0 tenant (`*-dtwo.us.auth0.com`) → **dtwo** → \"sign in with your Dtwo account\"\n  - any other issuer (Okta, Entra, etc.) → **custom** → \"sign in with your organization's identity provider\"\n  - `authentication.enabled: false` → **none** → \"This connection doesn't ask for a sign-in, so it connects straight away.\"\n\nDerive the MCP server name used in commands and config as the kebab-cased gateway name (`Acme Prod` →\n`acme-prod`), falling back to `dtwo-gateway` if unnamed. For Claude Desktop's connector name, prefer something\na person would recognize — `Dtwo` unless the user says otherwise.\n\n**Filter out non-work servers.** Gateways often carry development scaffolding a colleague would not recognize:\necho servers, pass-through-auth dev entries, anything on `host.docker.internal` or `localhost` with a name like\n`echo`, `test`, `probe`, `my-*-mcp`. Propose leaving those off the page and confirm, rather than listing them\nbeside Salesforce and Slack.\n\n## Step 3 — Pick the AI client\n\nAsk which client the instructions are for: **Claude Code**, **Claude Desktop**, **Cursor**, or **Codex**.\n\nThe answer names the document — carry it into both the headline and the opening paragraph. The page is always\nwritten for one specific client, and saying so up top is what tells a reader at a glance whether it applies to\nthem.\n\n**Validate Claude Desktop first.** Its custom connector is added through Anthropic's UI and connects from\noutside the user's machine, so the gateway URL must be HTTPS and must not be a loopback host (`localhost`,\n`127.0.0.1`, `::1`). If the chosen gateway fails that test, say Claude Desktop can't reach this gateway and\noffer Claude Code, Cursor or Codex instead — all three run locally.\n\n## Step 4 — Ask about org-wide configuration\n\nOnly two clients can be configured centrally. Ask this question **only** for them:\n\n- **Claude Desktop** — a Team/Enterprise Owner can add the connector under Organization settings → Connectors,\n  making it available to everyone. Ask: \"Has a Dtwo admin already added this connector for the whole organization?\"\n- **Claude Code** — `managedMcpServers` in managed settings (MDM profile, registry policy, `managed-settings.json`,\n  or server-managed settings) delivers the server to every user pre-configured. Requires Claude Code v2.1.259+.\n  Ask the same question.\n\n**Do not ask for Cursor or Codex.** Neither can provision a server centrally:\n\n- Cursor admins get an allowlist and a team marketplace, but adding a server to the allowlist does not push it\n  to users' machines — team members still configure it themselves.\n- Codex managed configuration treats `mcp_servers` purely as an approved list. There is no provisioning mechanism.\n\nWhen the answer is yes, the \"add it yourself\" step is dropped and replaced by a \"don't see it?\" fallback note.\n\n## Step 5 — Build the document\n\nWrite the HTML to a temporary directory, render it, and save the PDF where the user can reach it — the current\nworking directory by default, or `/mnt/user-data/outputs/` when running in Cowork. Name the file after the\nclient (`dtwo-claude-desktop-onboarding.pdf`) so someone holding several can tell them apart.\n\nFetch the Dtwo mark and recolour it for the dark masthead:\n\n```bash\ncurl -sS -L https://www.dtwo.ai/favicon.svg -o logo.svg\nsed 's/fill=\"#02329F\"/fill=\"#FFFFFF\"/g' logo.svg > logo-white.svg\n# embed both as data:image/svg+xml;base64,<...> in the HTML\n```\n\nRender with headless Chrome. The binary's location varies by machine — probe for it rather than hardcoding:\n\n```bash\nfor c in \\\n  \"/Applications/Google Chrome.app/Contents/MacOS/Google Chrome\" \\\n  \"/Applications/Chromium.app/Contents/MacOS/Chromium\" \\\n  \"$(command -v google-chrome)\" \"$(command -v chromium)\" \"$(command -v chromium-browser)\" \\\n  /opt/pw-browsers/chromium-*/chrome-linux/chrome ; do\n  [ -x \"$c\" ] && CHROME=\"$c\" && break\ndone\n\"$CHROME\" --headless --no-sandbox --disable-gpu --no-pdf-header-footer \\\n  --print-to-pdf=guide.pdf --virtual-time-budget=3000 \"file://$PWD/guide.html\"\n```\n\nIf no Chrome is found, say so and offer the HTML file instead — it prints to PDF correctly from any browser\nwith background graphics enabled. Do not silently fall back to a different renderer; the layout is tuned for\nChrome's print engine.\n\nOfficial logos for many connected systems are at `https://docs.dtwo.ai/logos/<name>.svg` (hubspot, apollo,\nslack, granola, salesforce, notion, github, linear, stripe, atlassian, ms365, google-drive, gmail,\ngoogle-calendar, google-sheets, google-docs, zoom, box, dropbox, airtable, asana, canva, datadog, glean,\nmonday, servicenow, splunk, docusign, gusto, zapier). Use them if the user wants real marks; otherwise use the\ncoloured accent bar in the template. Never hand-draw a brand logo.\n\n## Page structure\n\nLetter width, four zones in this order. One page is the target, not a constraint — see **Page length**:\n\n1. **Masthead** (dark navy) — Dtwo mark + wordmark, \"Getting started\" tag, two-line headline naming the client,\n   and a two-sentence opening.\n2. **What's in the package** — one card per connected system: coloured accent bar, name, role label,\n   one-sentence description.\n3. **Setup instructions** — the per-client steps below, plus a Connector URL bar and a caveat note where they apply.\n4. **How to use it** — three example asks that chain the gateway's actual servers, each with a small\n   \"A → B → C\" caption.\n\nFooter: Dtwo mark and a live `docs.dtwo.ai` hyperlink. No placeholder contact text.\n\n### Headline\n\n**The headline names the client the document was built for. Never write \"your AI assistant\" in the title** —\nthe reader is being handed instructions for one specific tool, and the title should say which.\n\nLine 1 is `Give {CLIENT}`; line 2 carries the accent colour:\n\n| client | headline |\n|---|---|\n| Claude Desktop | **Give Claude Desktop** / *secure access to your work tools.* |\n| Claude Code | **Give Claude Code** / *secure access to your work tools.* |\n| Cursor | **Give Cursor** / *secure access to your work tools.* |\n| Codex | **Give Codex** / *secure access to your work tools.* |\n\nAll four fit the masthead at 29pt on two lines.\n\n### Opening paragraph\n\n**The opening names the client too.** The first sentence says what Dtwo does for that specific product, so a\nreader who skims only the masthead knows both what this is and whether it applies to them. Substitute\n`{CLIENT}` for the subject — never \"your AI assistant\":\n\n> Dtwo connects {CLIENT} to the systems you use every day through one secure connection. It works in those\n> systems directly, pulling data and making updates, so there's no tab-switching or copy-and-paste.\n\nSo, for Claude Desktop:\n\n> Dtwo connects Claude Desktop to the systems you use every day through one secure connection. It works in\n> those systems directly, pulling data and making updates, so there's no tab-switching or copy-and-paste.\n\nNaming the product twice in the masthead is deliberate, not an accident to edit out. Keep the second sentence\nfree of the name — \"It works in those systems directly\" — so the repetition lands once and then moves on.\n\"Give your AI assistant secure access to your work tools.\" with a matching generic opening is the\nclient-neutral fallback, used only when the user asks for one.\n\n## Per-client setup steps\n\n`{NAME}` = connector/server name. `{URL}` = gateway MCP URL. `{IDP}` = \"your Dtwo account\" or \"your\norganization's identity provider\".\n\n### Claude Desktop — user adds it (4 steps + URL bar)\n\n1. **Add the connector** — In Claude Desktop, open **Settings → Connectors** and select **Add custom connector**. Name it {NAME} and paste the URL below.\n2. **Sign in** — Select **Connect**. Claude opens your browser so you can sign in with {IDP}.\n3. **Switch it on** — Start a new chat, open the dropdown in the chat box, choose **Connectors**, and switch {NAME} on. A connector that's added but left off is never called.\n4. **Check it worked** — Ask Claude what tools it has through {NAME}. It should list the tools from each of the systems above.\n\nURL bar: `{URL}`. Note: \"Your Claude organization owner may need to enable custom connectors for your account.\nIf Claude Desktop doesn't offer the option, ask an owner to enable it.\"\n\n### Claude Desktop — org already configured (3 steps, no URL bar)\n\n1. **Connect** — Open **Settings → Connectors**. {NAME} is already listed for your organization. Select **Connect** and sign in with {IDP} when the browser opens.\n2. **Switch it on** — Start a new chat, open the dropdown in the chat box, choose **Connectors**, and switch {NAME} on. A connector that's added but left off is never called.\n3. **Check it worked** — Ask Claude what tools it has through {NAME}. It should list the tools from each of the systems above.\n\nNote: \"Don't see {NAME} in your connector list? Your admin hasn't added it yet — check with them.\"\n\n### Claude Code — user adds it (3 steps)\n\n1. **Add the connection** — Run this in your terminal: `claude mcp add --transport http {NAME} {URL}` (append ` --client-id <CLIENT_ID>` when the gateway uses a custom identity provider).\n2. **Sign in** — Run `/mcp`, select {NAME}, and sign in with {IDP}.\n3. **Check it worked** — Run `/mcp` again. {NAME} shows as connected, with its tools listed underneath.\n\nOffer the `.mcp.json` form as an alternative if the user prefers a file:\n\n```json\n{\n  \"mcpServers\": {\n    \"{NAME}\": {\n      \"type\": \"http\",\n      \"url\": \"{URL}\"\n    }\n  }\n}\n```\n\n### Claude Code — org already configured (3 steps)\n\n1. **Open Claude Code** — {NAME} is already set up by your organization. There's nothing to install.\n2. **Sign in** — Run `/mcp`, select {NAME}, and sign in with {IDP}.\n3. **Check it worked** — Run `/mcp` again. {NAME} shows as connected, with its tools listed underneath.\n\nNote: \"Don't see it? Your organization's settings may not have reached this machine yet, or Claude Code may\nneed updating to v2.1.259 or later.\"\n\n### Cursor (3 steps)\n\n1. **Add the connection** — Add this to `~/.cursor/mcp.json` for every project, or `.cursor/mcp.json` for one project:\n\n```json\n{\n  \"mcpServers\": {\n    \"{NAME}\": {\n      \"url\": \"{URL}\",\n      \"auth\": {\n        \"CLIENT_ID\": \"<CLIENT_ID>\"\n      }\n    }\n  }\n}\n```\n\n(drop the `auth` block when the gateway has authentication switched off)\n\n2. **Enable and sign in** — In Cursor, open **Customize → MCPs** and enable the server. Complete the browser sign-in with {IDP}.\n3. **Check it worked** — In **Customize → MCPs**, confirm {NAME} is enabled and its tools are listed.\n\nNote: \"If your admin has published Dtwo to your team marketplace, install it from there instead of pasting this in.\"\n\n### Codex (3 steps)\n\n1. **Add the connection** — With the Codex CLI installed, run: `codex mcp add {NAME} --url {URL}` (append ` --oauth-client-id '<CLIENT_ID>'` for a custom identity provider).\n2. **Sign in** — Complete the browser sign-in with {IDP}. If sign-in doesn't start, run `codex mcp login {NAME}`.\n3. **Check it worked** — Start a new task in Codex and ask which tools it has through {NAME}. It should list the tools from the systems above.\n\n## Config examples in the document\n\nAny command or config block printed on the page is something a reader will retype or paste. Correctness beats\ncompactness every time.\n\n- **Pretty-print JSON across multiple lines with two-space indentation.** Never collapse a config to one line\n  to save vertical space. A reader who mistypes a collapsed brace gets an error they can't diagnose.\n- Keep `white-space: pre-wrap` on the code block so the indentation survives and long URLs still wrap.\n- Never break a shell command across lines without a trailing `\\\\`. A wrapped command that looks like two\n  commands is worse than one that overflows.\n- If an indented block makes the page too tall, that is a page-length decision (below), not a reason to\n  reformat the code.\n\n## System descriptions\n\nOne line each, written for a colleague. For a server not listed, write a plain one-sentence description of what\nthat product does and pick a colour close to its brand.\n\n| server | label | role | description | colour |\n|---|---|---|---|---|\n| hubspot | HubSpot | Your CRM | Look up companies, contacts and deals. Search records, read pipeline reporting, log activity. | `#FF7A59` |\n| salesforce | Salesforce | Your CRM | Look up accounts, opportunities and contacts, run reports, and update records. | `#00A1E0` |\n| apollo | Apollo.io | Prospecting | Find people and companies that match who you sell to, and enrich the contacts you already have. | `#5C4CE5` |\n| slack | Slack | Team context | Search the channels you're already in, catch up on history you missed, post back to the team. | `#4A154B` |\n| granola | Granola | Meeting notes | Pull notes and transcripts from your calls, so answers come from what was actually said. | `#E8A33D` |\n| ms365 | Microsoft 365 | Mail and files | Reach your mail, calendar, Teams messages, SharePoint files and OneNote. | `#D83B01` |\n| drive / google-drive | Google Drive | Files | Search your documents and pull what's in them. | `#1FA463` |\n| mail / gmail | Gmail | Your inbox | Search mail, read threads, and draft replies. | `#EA4335` |\n| calendar | Google Calendar | Your schedule | See what's on, find free time, and check who's attending. | `#4285F4` |\n| sheets | Google Sheets | Spreadsheets | Read and update spreadsheet data. | `#0F9D58` |\n| google-docs | Google Docs | Documents | Read and edit documents. | `#4285F4` |\n| notion | Notion | Your workspace | Search pages and databases, and write updates back. | `#2F3437` |\n| atlassian | Atlassian | Issues and docs | Search Jira issues and Confluence pages, and create or update work items. | `#0052CC` |\n| github | GitHub | Your code | Search repositories, read code and issues, and check pull requests. | `#24292F` |\n| linear | Linear | Issue tracking | Find issues, check what's in flight, and file new work. | `#5E6AD2` |\n| stripe | Stripe | Payments | Look up customers, charges and subscriptions. | `#635BFF` |\n| datadog | Datadog | Monitoring | Query metrics, logs and monitors. | `#632CA6` |\n| zapier | Zapier | Everything else | Reach thousands of other apps through your existing Zapier connections. | `#FF4F00` |\n\n## Example asks\n\nWrite three, each chaining real servers from this gateway, using the reader's language rather than tool names.\nGive each a caption naming the systems in order. Two-system examples are fine when the gateway is small. With\nonly one server, drop the captions and write three single-system asks instead.\n\nMatch the examples to what the gateway actually holds: a CRM-and-notes gateway earns call-logging and\nfollow-up examples; an issues-and-chat gateway earns release-status and bug-filing ones. Generic sales examples\non an engineering gateway are the fastest way to make the page feel untrue.\n\n## HTML template\n\n```html\n<!DOCTYPE html>\n<html lang=\"en\"><head><meta charset=\"utf-8\"><title>{TITLE}</title>\n<style>\n  @page { size: Letter; margin: 0; }\n  :root{ --ink:#081B2E; --blue:#02329F; --blue2:#344FA0; --coral:#EA5D4C;\n    --mist:#EDF0F5; --muted:#5A6B7E; --line:#DCE2EA; }\n  *{ box-sizing:border-box; margin:0; padding:0; }\n  html,body{ -webkit-print-color-adjust:exact; print-color-adjust:exact; }\n  body{ font-family:\"Carlito\",\"Liberation Sans\",\"Helvetica Neue\",Arial,sans-serif; color:var(--ink); font-size:10pt; line-height:1.45; }\n  .page{ width:8.5in; height:11in; position:relative; overflow:hidden; background:#fff; }\n  .mast{ background:var(--ink); color:#fff; padding:.4in .68in .34in; position:relative; }\n  .rule-top{ position:absolute; top:0; left:0; right:0; height:6px;\n    background:linear-gradient(90deg,var(--blue) 0%,var(--blue2) 45%,var(--coral) 100%); }\n  .mast-head{ display:flex; justify-content:space-between; align-items:baseline; }\n  .lockup{ display:flex; align-items:center; gap:12px; }\n  .lockup img{ width:33px; height:35px; display:block; }\n  .wordmark{ font-size:13pt; font-weight:700; letter-spacing:.15em; text-transform:uppercase; }\n  .wordmark span{ color:var(--coral); }\n  .mast-head .tag{ font-size:8pt; letter-spacing:.2em; text-transform:uppercase; color:#8FA6C4; font-weight:700; }\n  h1{ margin-top:.16in; font-size:29pt; line-height:1.05; letter-spacing:-.025em; font-weight:700; }\n  h1 .accent{ color:#9FC0FF; }\n  .mast p{ margin-top:.13in; font-size:10.8pt; line-height:1.5; color:#C3D3E6; max-width:6.6in; }\n  .body{ padding:.34in .68in 0; }\n  .sec{ margin-top:.32in; } .sec:first-child{ margin-top:0; }\n  .kicker{ font-size:8pt; letter-spacing:.2em; text-transform:uppercase; color:var(--blue);\n    font-weight:700; display:flex; align-items:center; gap:10px; }\n  .kicker::after{ content:\"\"; flex:1; height:1px; background:var(--line); }\n  .systems{ display:flex; flex-wrap:wrap; gap:13px; margin-top:.22in; }\n  .sys{ flex:1; border:1px solid var(--line); border-radius:11px; padding:15px 14px 16px; }\n  .sys .bar{ width:30px; height:4px; border-radius:2px; }\n  .sys h3{ font-size:11.5pt; margin-top:11px; letter-spacing:-.01em; }\n  .sys .role{ font-size:8.4pt; color:var(--blue); text-transform:uppercase; letter-spacing:.08em; font-weight:700; margin-top:2px; }\n  .sys p{ font-size:9pt; color:var(--muted); margin-top:8px; line-height:1.5; }\n  .steps{ display:flex; gap:13px; margin-top:.22in; }\n  .step{ flex:1; background:var(--mist); border-radius:11px; padding:15px 14px 16px; }\n  .step .n{ width:23px; height:23px; border-radius:50%; background:var(--ink); color:#fff;\n    display:flex; align-items:center; justify-content:center; font-size:9.5pt; font-weight:700; }\n  .step h3{ font-size:11pt; margin-top:10px; }\n  .step p{ font-size:9pt; color:var(--muted); margin-top:6px; line-height:1.5; }\n  .step p strong{ color:var(--ink); font-weight:700; }\n  .step code{ font-family:\"Liberation Mono\",Menlo,Consolas,monospace; font-size:8.1pt; color:var(--blue);\n    background:#fff; border:1px solid #D6E1F7; padding:6px 8px; border-radius:5px;\n    display:block; margin-top:8px; overflow-wrap:break-word; line-height:1.5;\n    white-space:pre-wrap; }  /* pre-wrap keeps JSON indentation and still wraps long URLs */\n  .urlbar{ margin-top:.14in; display:flex; align-items:center; gap:14px;\n    border:1px solid #D6E1F7; background:#F4F7FD; border-radius:9px; padding:11px 15px; }\n  .urlbar .lbl{ font-size:8pt; letter-spacing:.14em; text-transform:uppercase; color:var(--muted); font-weight:700; white-space:nowrap; }\n  .urlbar .val{ font-family:\"Liberation Mono\",Menlo,Consolas,monospace; font-size:10pt; color:var(--blue); font-weight:700; }\n  .note{ font-size:8.5pt; color:var(--muted); margin-top:9px; line-height:1.45; }\n  .ex{ display:flex; gap:14px; margin-top:.22in; }\n  .exq{ flex:1; border-left:3px solid var(--coral); padding:2px 0 2px 12px; }\n  .exq p{ font-size:9.4pt; line-height:1.48; }\n  .exq .m{ font-size:7.9pt; letter-spacing:.09em; text-transform:uppercase; color:var(--muted); font-weight:700; margin-top:6px; }\n  .foot{ position:absolute; left:.68in; right:.68in; bottom:.34in; border-top:1px solid var(--line);\n    padding-top:10px; display:flex; font-size:8.5pt; color:#93A3B5; }\n  .foot .right{ display:flex; align-items:center; gap:8px; }\n  .foot .right img{ width:15px; height:16px; display:block; opacity:.85; }\n  .foot a{ color:var(--blue); text-decoration:none; font-weight:700; }\n</style></head>\n<body><section class=\"page\">\n  <div class=\"mast\">\n    <div class=\"rule-top\"></div>\n    <div class=\"mast-head\">\n      <div class=\"lockup\"><img src=\"{LOGO_WHITE}\" alt=\"Dtwo\"><div class=\"wordmark\">Dtwo<span>.</span></div></div>\n      <div class=\"tag\">Getting started</div>\n    </div>\n    <h1>Give {CLIENT}<br><span class=\"accent\">secure access to your work tools.</span></h1>\n    <p>{OPENING}</p>\n  </div>\n  <div class=\"body\">\n    <div class=\"sec\">\n      <div class=\"kicker\">What's in the package</div>\n      <div class=\"systems\">{SYSTEM_CARDS}</div>\n    </div>\n    <div class=\"sec\">\n      <div class=\"kicker\">Setup instructions</div>\n      <div class=\"steps\">{STEP_CARDS}</div>\n      {URL_BAR}\n      {NOTE}\n    </div>\n    <div class=\"sec\">\n      <div class=\"kicker\">How to use it</div>\n      <div class=\"ex\">{EXAMPLES}</div>\n    </div>\n  </div>\n  <div class=\"foot\"><span class=\"right\"><img src=\"{LOGO_BLUE}\" alt=\"\"><a href=\"https://docs.dtwo.ai\">docs.dtwo.ai</a></span></div>\n</section></body></html>\n```\n\nSet the `<title>` to the client-specific headline. If `pikepdf` or `exiftool` is available, set the PDF metadata\ntitle to match; skip it silently if neither is installed.\n\n## Page length\n\n**One page is the target, not a rule.** A gateway with four or five systems fits comfortably. A gateway with\nten does not, and squeezing it in produces a document nobody can read. When the content does not fit, let it\nrun to a second page.\n\n### Type floors — never go below these to save a page\n\n| element | minimum |\n|---|---|\n| headline | 24pt |\n| opening paragraph | 10pt |\n| card description | 8.5pt |\n| step body | 8.5pt |\n| example ask | 8.5pt |\n| code block | 8pt |\n\nTrimming spacing is fine. Going under these sizes is not. If it still doesn't fit, add the page.\n\n### Card grid by server count\n\n| systems | layout | expect |\n|---|---|---|\n| 1–4 | one row, `flex:1` each | one page |\n| 5–8 | wrap to rows of four, `flex:0 0 calc(25% - 10px)` | one page, tight |\n| 9+ | rows of four, same as above | two pages |\n\n`.systems` already carries `flex-wrap:wrap` in the template, so wrapping only needs the per-card `flex` basis\nabove. With four or fewer, leave `flex:1` and they fill the row.\n\n### Going to two pages\n\nThe single-page template pins the page to `11in` with `overflow:hidden` and absolutely positions the footer,\nso a second page's content is silently **clipped**, not flowed. Switch these before rendering anything longer:\n\n```css\n.page{\n  width:8.5in;\n  min-height:11in;   /* was: height:11in */\n  height:auto;\n  overflow:visible;  /* was: hidden — this is what clips page 2 */\n}\n.foot{\n  position:static;   /* was: absolute with bottom:.34in */\n  margin:.5in .68in .34in;\n}\n.sys, .step, .exq{ break-inside:avoid; }\n.sec{ break-inside:avoid; }\n```\n\nPut the break between **What's in the package** and **Setup instructions**, so the masthead and the system\ncards carry page one and the steps start clean on page two. Never split a row of cards, a row of steps, or a\nsingle step across the break. Force it with `break-before:page` on the setup section if the natural break\nlands badly.\n\nThe footer flows to the end of the last page. That is correct — it is a sign-off, not a running footer.\n\n### Always look at the result\n\nRender to PNG and Read every page. Prefer poppler, which shows the PDF exactly as printed:\n\n```bash\npdftoppm -png -r 90 guide.pdf op        # one op-N.png per page\n```\n\nIf `pdftoppm` is not installed, fall back to the Chrome you already found — don't ask the user to install\nanything:\n\n```bash\n\"$CHROME\" --headless --no-sandbox --disable-gpu --hide-scrollbars \\\n  --window-size=816,1056 --screenshot=op.png \"file://$PWD/guide.html\"\n```\n\n`816×1056` is one Letter page at 96 dpi. For a two-page document use `--window-size=816,2112`. The screenshot\nrenders screen layout, not print, so it catches clipping, overflow and footer collisions but does **not** show\nwhere the print page break falls — on a two-page document, also confirm the PDF has two pages\n(`grep -ao '/Count [0-9]*' guide.pdf | awk '{print $2}' | sort -n | tail -1` prints the page count) and tell the user the break\nposition was checked from the CSS rather than the rendered PDF.\n\nConfirm: nothing clipped at a page edge, no card or step orphaned alone at the top of page two, no text\ncolliding with the footer, and page one not left half empty by a premature break.\n\nIf the result is one page with a lot of empty space at the bottom, push `.sec` margin-top, `.body`\npadding-top, and card padding up until the content fills it. Starting points for the common shapes:\n\n| cards / steps | `.sec` margin-top | `.body` padding-top | card padding |\n|---|---|---|---|\n| 4 cards, 4 steps | `.28in` | `.3in` | `14px 13px 15px` |\n| 4 cards, 3 steps | `.36in` | `.36in` | `15px 13px 16px` |\n| 3 cards, 3 steps | `.42in` | `.4in` | `17px 16px 18px` |\n\n## Before delivering\n\n- Confirm the word \"gateway\" appears nowhere in the rendered text: `pdftotext guide.pdf - | grep -i gateway`.\n  Without `pdftotext`, check the HTML's visible text instead — it's the same content:\n  `perl -0pe 's/<style.*?<\\/style>//gs; s/<[^>]*>//g' guide.html | grep -i gateway`\n- Confirm the headline **and** the opening paragraph both name the chosen client, not \"your AI assistant\".\n- Confirm the URL and every command match the gateway's real values. Nothing invented.\n- Confirm no placeholder text survives unless the user asked for one.\n- Confirm every config block is indented across multiple lines, not collapsed onto one.\n- On a two-page document, confirm nothing is clipped and the break falls where you intended.\n\nTell the user which gateway, client and configuration the document assumes — the same gateway produces a\ndifferent page for each combination, and that line is what stops the wrong one being forwarded.\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}