Closes two more named rev-199 radar candidates at the templates axis (independent toy / hobby shops with named-supplier continuity + age-gating + safety hygiene per CPSIA + ASTM F963 + holiday inventory cadence with named-buyer ordering window in February-May + named-recall response with same-day named-pull on every CPSC notice, and independent framing / mat-board ateliers with named-piece chain-of-custody + named-substrate + named-mat + named-glazing discipline with named-conservation-grade for any named-archival piece + rush-job hygiene with named-deadline + named-rush-fee + named-substitution-risk-disclosure + named-on-time-confidence rating + named-conservation-grade supplier continuity) bringing the templates cluster to seventy-three named verticals — the rev-199 next-radar wave queued small independent toy / hobby shops + independent framing / mat-board ateliers as the rev-200/201 candidates, with rev-200 deliberately stepping off the templates grind for accessibility + milestone + per-category recent endpoint work, and rev-201 picking the radar back up. Plus extends the rev-192 /api/v1/onboarding-templates/categories endpoint with a new per-category `latestLaunch` block (most-recently-shipped template per category with its key + name + rev + date) so MCP hosts rendering 'browse Loop Desk's industry coverage by freshness' get the per-category freshness answer in the same call as the rev-198 depth answer — pairs with `coverageDepth` as the depth + freshness signal pair on every category row. Plus mirrors the rev-201 freshness signal at the human-readable surface: the /templates hero category-chip tooltip now surfaces 'newest rev N (YYYY-MM-DD)' alongside the existing 'N templates · M memory entries · K sample signals' depth signal so procurement reviewers landing on /templates see depth + freshness on one hover. The OpenAPI 3.1 spec types the new `latestLaunch` field with full schema + count copy bumps 71 → 73 across the rev-172 listing endpoint description in lockstep — the cadence pattern from rev 78 onward (every dashboard primitive gets typed in the OpenAPI 3.1 spec in the same cycle it ships) reaches its 109th unbroken rev with rev 201. Plus 16 new SEO keywords cover the toy / hobby + framing / mat-board axes (AI for toy shops + AI for hobby shops + AI for game shops + AI for CPSC recall response + AI for CPSIA compliance + AI for ASTM F963 toy safety + AI for holiday inventory cadence + AI for framing ateliers + AI for custom framing shops + AI for mat-board cutters + AI for conservation framing + AI for archival framing + AI for piece chain-of-custody + AI for rush-job hygiene in framing) (rev 201)
Two more onboarding templates — Independent toy / hobby shops + Independent framing / mat-board ateliersCloses the named rev-199 radar wave at two more underserved owner-led retail + specialty segments where regulated discipline (CPSIA + ASTM F963 toy safety on the toy/hobby side, named-conservation-grade material continuity on the framing/mat-board side) is the load-bearing differentiator against generic chain retail. Independent toy / hobby shops (4 high-importance memory entries: named-supplier continuity with named-primary + named-secondary on every named-product line crossing 2% of trailing-12-month revenue + sub-policy on rep + acquisition changes, age-gating + safety hygiene per CPSIA + ASTM F963 with named-age-band + named-safety-cert reference on file in named-supplier-record + named-display posture rule on small-parts toys + named-pellet items + named-craft-chemicals, holiday inventory cadence with named-buyer ordering window in February-May for the named-Q4 cycle + named-Q4-allocation target tied to named-prior-year-Q4 + named-trend-adjustment + named-supplier-allocation-confirmation, named-recall response with same-day named-pull from named-floor + named-website + named-supplier consult on every CPSC notice + named-customer-record-pull on named-affected-batch + 1 sample mid-Q4 named-supplier allocation shortage signal on a named-hot-product-line). Independent framing / mat-board ateliers (4 high-importance memory entries: named-piece chain-of-custody with named-condition-report + named-photographs at named-intake + named-bench-handoff at every named-stop signed by the named-bench-worker + named-pickup-signoff at named-customer-pickup, named-substrate + named-mat + named-glazing discipline with named-conservation-grade for any named-archival piece + sub-policy on named-sentimental + named-monetary-value > $500 pieces, rush-job hygiene with named-deadline + named-rush-fee + named-substitution-risk-disclosure + named-on-time-confidence rating on every <7-day named-quote, named-conservation-grade supplier continuity with named-quarterly named-supplier review + named-second-source review on any named-supplier above 5% named-quality-rejection or 2-week named-lead-time miss + 1 sample mid-job named-substrate-substitution disclosure-gap signal on a named-archival-piece). Two new OnboardingTemplateKey enum values (toy_hobby_shop in retail-ecommerce, framing_mat_board in manufacturing-specialty) extend the rev-19 enum without migration. The templates cluster is now seventy-three named verticals deep — closes the day-1 starvation-point story across two more underserved owner-led segments where regulated discipline (CPSC + CPSIA + ASTM F963 toy safety; named-conservation-grade material continuity) is the load-bearing differentiator against generic AI tools that don't know the regulatory vocabulary.
Per-category latestLaunch metadata on /api/v1/onboarding-templates/categories — closes the freshness-axis gap on the rev-192 taxonomy endpointUntil rev 201 the rev-192 /api/v1/onboarding-templates/categories endpoint carried per-category depth (rev 198 `coverageDepth` block) + per-category count + archive URL — but no freshness signal. MCP hosts rendering 'which category got new coverage most recently?' had to fetch the rev-172 full listing + the rev-176 TEMPLATE_LAUNCH map and aggregate client-side, OR fetch the rev-200 per-category recent endpoint per category. Rev 201 closes that with one new field per category row: `latestLaunch: { templateKey, templateName, rev, date } | null`. Pure derived state from the rev-176 TEMPLATE_LAUNCH map walked once per request + the rev-190 TEMPLATE_CATEGORY_BY_KEY filter — no schema cost, no migration. Null when the category has no templates yet (defensive — the 10 industry buckets all currently have ≥2 templates so this null branch is reserved for future-proofing). Pairs naturally with `coverageDepth` (rev 198) as the depth + freshness signal pair on every category row, so 'browse by industry' MCP-host UIs can sort by depth OR by freshness with one bearer-less GET. The OpenAPI 3.1 spec types the new field with full schema in lockstep — the cadence pattern from rev 78 onward (every v1 enhancement gets typed in the OpenAPI 3.1 spec in the same cycle it ships) reaches its 109th unbroken rev with rev 201. Strategic significance: closes the named rev-200/v1 'category freshness' gap that the per-category recent endpoint (rev 200) addressed at the per-category-array shape — rev 201 brings the same signal to the taxonomy endpoint as a single field so callers reading the categories list once get both depth + freshness without a follow-up call per category.
/templates hero category-chip tooltip now surfaces freshness alongside depth — mirrors v1 latestLaunch at the human-readable surfaceRev 201 mirrors the new v1 `latestLaunch` field at the human-readable /templates surface: the rev-197 per-category chip cluster's tooltip (which already surfaced depth via 'N templates · M memory entries · K sample signals' since rev 198) now ALSO surfaces 'newest rev N (YYYY-MM-DD)' as a freshness tail so procurement reviewers landing on /templates from a per-vertical search snippet see depth + freshness on one hover. Pure derived state from the rev-176 TEMPLATE_LAUNCH map — no schema cost. New `CategoryStat` type adds `latestRev` + `latestDate` + `latestDateMs` fields to the existing getCategoryStats aggregator. The tooltip stays scannable on first glance (the chip face itself shows only category name + count) but the depth + freshness answer is one hover away. Strategic significance: closes the depth+freshness symmetry across both reading horizons (protocol-bound v1 + human-readable HTML). Pairs naturally with the rev-176 60-day 'New' pill on every per-template card + the rev-196 'Recently added' featured strip + the rev-200 per-category recent strip as the four-axis freshness story across every public marketing surface on the templates cluster.
Templates page count + radar copy refresh + 16 new SEO keywords + OpenAPI typed coverage (109th unbroken cadence rev)Templates page count copy bumps 'Seventy-one verticals today' → 'Seventy-three verticals today' across hero, metadata title, OpenGraph + Twitter description, JSON-LD CollectionPage block, and templates-cta. Sixteen new SEO keywords on the templates metadata covering toy / hobby + framing / mat-board axes (AI for toy shops, AI for independent toy retailers, AI for hobby shops, AI for game shops, AI for CPSC recall response, AI for CPSIA compliance, AI for ASTM F963 toy safety, AI for holiday inventory cadence, AI for framing ateliers, AI for custom framing shops, AI for mat-board cutters, AI for conservation framing, AI for archival framing, AI for piece chain-of-custody, AI for rush-job hygiene in framing). Don't see your vertical? CTA copy refreshes the next-radar list — replaced with independent specialty fishing / outdoor outfitters (named-license currency + named-charter continuity + named-safety-incident hygiene), independent bookbinders / paper conservators (named-substrate + named-adhesive discipline + named-piece chain-of-custody adjacent to the rev-201 framing axis), independent stationery / pen shops (named-supplier continuity + named-collectibles authentication), and small independent cheesemongers (named-affinage cycle + named-supplier continuity + named-shrinkage discipline) now that toy/hobby + framing/mat-board are shipped. The rev-172 listing endpoint description bumps from 71 → 73 verticals in the OpenAPI 3.1 spec + the new latestLaunch field is fully typed on the rev-192 categories endpoint response schema — the cadence pattern from rev 78 onward (every dashboard primitive gets typed in the OpenAPI 3.1 spec in the same cycle it ships) reaches its 109th unbroken rev with rev 201.
Start free — there are no metered credits to run out.