git:20260514.bcb35bf to git:20260902.f794219

1 added, 156 removed. Audit B to B.

What this update changes in the checks

This update trips no new check.

It clears 1 check: No script tag.

A tripped check is a label, not a verdict: read the matched text and the lines below. This week's updates that newly trip a check.

- # Duct Site — Claude Code instructions
-
- Static marketing site for [getduct.ai](https://getduct.ai). Pure HTML/CSS/JS.
-
- ## Site strategy
-
- Two content types, two jobs:
- - **Landing pages** (`for-*.html`) — paid ad experiments. Each page targets a specific audience or solution angle. Fast to create, easy to A/B by URL. Goal: validate conversion before investing in a channel or audience.
- - **Blog** (`blog/posts/`) — organic SEO. Written for keyword clusters, not just announcements. Goal: compound traffic from search.
-
- When adding either, ask: *what's the hypothesis being tested?* Put it in a `<!-- EXPERIMENT: ... -->` comment near the top of `<body>`.
-
- ## Stack constraints
-
- - **NO build tools.** No npm, Vite, Webpack, Rollup, or package manager setup.
- - No frameworks (React, Vue, Astro, Alpine, etc.).
- - JavaScript should stay vanilla and ES5-compatible where practical.
-
- ## Local dev
-
- ```bash
- python3 -m http.server 8090 --directory site
- ```
-
- Then open `http://localhost:8090/`.
-
- ## URL → file mapping
-
- | Production URL | File |
- |---|---|
- | `https://getduct.ai/` | `site/index.html` |
- | `https://getduct.ai/for-product-intelligence` | `site/for-product-intelligence.html` |
- | `https://getduct.ai/for-organic-growth` | `site/for-organic-growth.html` |
- | `https://getduct.ai/for-paid-ads` | `site/for-paid-ads.html` |
- | `https://getduct.ai/blog/` | `site/blog/index.html` |
- | `https://getduct.ai/blog/post?slug=SLUG` | `site/blog/post.html` |
-
- ## Shared assets
-
- | File | Purpose |
- |---|---|
- | `site/assets/duct.css` | All brand styles |
- | `site/assets/duct.js` | GTM init, scroll reveal, nav shadow, `submitForm()` |
- | `site/assets/config.js` | `DUCT_CONFIG.gtm` only |
- | `site/assets/demo.css` | All shared interactive demo CSS (~800 lines) |
- | `site/assets/demo.js` | Shared demo JS engine (state machine, navigation, modal, hash routing) |
- | `site/assets/demo-paid-ads.js` | Paid Ads variant data + Engine A fill override |
- | `site/assets/demo-product.js` | Product Intelligence variant data |
- | `site/assets/demo-organic.js` | Organic Growth variant data |
-
- - Inside `site/` HTML files, root-level pages use `assets/`.
- - Blog files under `site/blog/` use `../assets/`.
- - `config.js` must load before `duct.js`.
-
- ## Interactive demo pattern
-
- Each `for-*.html` landing page that has a demo includes:
-
- ```html
- <!-- in <head>, after duct.css -->
- <link rel="stylesheet" href="assets/demo.css"/>
- ```
-
- ```html
- <!-- at end of <body>, before duct.js -->
- <script src="assets/demo-<variant>.js"></script>
- <script src="assets/demo.js"></script>
- <script src="assets/duct.js" defer></script>
- ```
-
- The per-variant file (`demo-<variant>.js`) sets `window.DUCT_DEMO_CONFIG` with:
-
- ```js
- window.DUCT_DEMO_CONFIG = {
- cfg: {
- min: 2, // minimum platforms before "Next" enables
- src: { PlatformName: 'API label', ... },
- defs: { metricKey: { hero, fmt, label, bar, ths, hide }, ... },
- cross: { metricKey: [...] or {level,pill,title,body,ownerName,assignee,followUp}, ... },
- kpiKeys: ['key1', 'key2', ...],
- kpiDefs: { key1: { fmt: 'p1' }, key2: { fmt: 'k', sum: true }, ... },
- defaultMetric: 'key1',
- defaultPlatforms: ['Plat1', 'Plat2'],
- sparkColor: '#hexcolor' // optional, defaults to #2563eb
- },
- data: D, // { PlatformName: { metricKey: { hero, k, r, s, sp, u }, ... } }
- fill: fillFn, // optional: custom fill function (paid-ads only)
- minHint: 2 // optional: hide #plat-hint when >= N platforms selected
- };
- ```
-
- `kpiDefs[key].sum: true` → sum across platforms; omit for average.
- `cross[metricKey]` accepts either an array `[level, pill, title, body, ownerName, assignee, followUp]` or a named-key object (both normalised internally).
-
- ### Adding a new demo variant
-
- 1. Create `site/assets/demo-for-x.js` with `window.DUCT_DEMO_CONFIG`.
- 2. Copy an existing `for-*.html`, update meta/hero/sections.
- 3. Swap demo step HTML (plat-grid buttons, metric-grid cards, analyzing lines, KPI chip IDs).
- 4. `<link demo.css>` in head; `<script demo-for-x.js>` + `<script demo.js>` at body end.
- 5. Add to `sitemap.xml`.
-
- ## Page `<head>` checklist
-
- Every HTML page must have:
- - canonical
- - description
- - robots
- - OG tags
- - Twitter tags
- - shared stylesheet
- - `config.js` then `duct.js`
- - GTM noscript iframe immediately after `<body>`
-
- ## Google Forms
-
- ```html
- <button class="btn btn-orange btn-lg"
- data-form-url="https://docs.google.com/forms/d/e/FORM_ID/formResponse"
- data-entry-id="entry.FIELD_ID"
- onclick="submitForm('INPUT_ID', this)">Get early access →</button>
- ```
-
- Copy the form attributes from `site/for-product-intelligence.html` unless the page needs a distinct form. Do not add a `<form>` element.
-
- ## New landing page variant (no demo)
-
- 1. Copy `site/for-product-intelligence.html` to a new `site/for-*.html` file.
- 2. Update title, canonical, nav subtitle, hero copy, and audience cards.
- 3. Add the new page to `site/sitemap.xml`.
-
- ## New landing page variant (with demo)
-
- Follow the **Adding a new demo variant** instructions above.
-
- ## New blog post
-
- Posts live in `site/blog/posts/<slug>.md` with required front matter:
- - `title`
- - `date`
- - `author`
- - `category`
- - `excerpt`
- - `readTime`
-
- ## Deploy
-
- Publish directory: `site/`.
-
- ## What not to do
-
- - Do not add npm tooling.
- - Do not create `.env` files.
- - Do not hardcode the GTM ID in page JavaScript.
- - Do not put page-specific styles into `site/assets/duct.css`; use an inline `<style>` block when needed.
-
+ AGENTS.md