[seanspeaks]

Summary

The friggframework.org announcement for Frigg 2.0.1, reframed around the release story in #660: "the integration backend for people and their agents." It is stacked on the trail-hero PR (#661). The trail backdrop is unchanged.

• Release strip: "Frigg 2.0.1 is out: the integration backend for people and their agents." There is also a 2.0 nav link and a v2.0.1 out now chip.
• Hero: a one-line edit to the lede. It now says 2.0 is the integration backend for people and their agents, built to run in production.
• "What's in 2.0" (#v2): the six cards are the pillars, in the site's existing card style:
  1. three ways to define an integration (code, a document, a catalogue entry);
  2. connections agents can use without seeing credentials;
  3. two app profiles;
  4. production by default;
  5. more than one host (AWS, Netlify);
  6. under the hood.
• "We run it ourselves": a note under the cards. Left Hook runs both profiles on 2.0: an internal agent tool server where every person's connections live in Frigg (operations, Netlify), and a product where customers' integrations are built from a catalogue or by chat (product, AWS).
• "Upgrade from 1.x" (#upgrade): the breaking-change list adds fail-closed encryption, the deprecated v1 API (still works), and Node 22.13+/24 with osls 4. The ^2.0.1 and Prisma ^6.19.3 install commands are unchanged.
• The footer version badge reads v2.0.1.

The cards describe work from open PRs that ships in 2.0.1 by decision. #660 lists every dependency and its status.

Merge on release day only

Keep this as a draft until npm view @friggframework/core dist-tags.latest prints 2.0.1, and #660's dependencies have landed. When #661 merges, retarget this PR to next.

Test plan

• Served locally and screenshotted the release strip, hero, #v2 and #upgrade at 1440px and 500px (headless Chrome's minimum width), with .reveal forced visible. No overflow; the cards collapse to one column on narrow screens.
• Public-repo name check on the diff: no client or unreleased product names
• Every link resolves after the docs default switches to 2.0 (/2.0/getting-started/whats-new-in-2.0, /2.0/guides/migrating-to-2.0)

📦 Published PR as canary version: 2.0.0--canary.662.6d3931c.0

✨ Test out this PR locally via:

npm install @friggframework/admin-scripts@2.0.0--canary.662.6d3931c.0
npm install @friggframework/core@2.0.0--canary.662.6d3931c.0
npm install @friggframework/devtools@2.0.0--canary.662.6d3931c.0
npm install @friggframework/eslint-config@2.0.0--canary.662.6d3931c.0
npm install @friggframework/prettier-config@2.0.0--canary.662.6d3931c.0
npm install @friggframework/schemas@2.0.0--canary.662.6d3931c.0
npm install @friggframework/serverless-plugin@2.0.0--canary.662.6d3931c.0
npm install @friggframework/test@2.0.0--canary.662.6d3931c.0
npm install @friggframework/ui@2.0.0--canary.662.6d3931c.0
# or 
yarn add @friggframework/admin-scripts@2.0.0--canary.662.6d3931c.0
yarn add @friggframework/core@2.0.0--canary.662.6d3931c.0
yarn add @friggframework/devtools@2.0.0--canary.662.6d3931c.0
yarn add @friggframework/eslint-config@2.0.0--canary.662.6d3931c.0
yarn add @friggframework/prettier-config@2.0.0--canary.662.6d3931c.0
yarn add @friggframework/schemas@2.0.0--canary.662.6d3931c.0
yarn add @friggframework/serverless-plugin@2.0.0--canary.662.6d3931c.0
yarn add @friggframework/test@2.0.0--canary.662.6d3931c.0
yarn add @friggframework/ui@2.0.0--canary.662.6d3931c.0

🤖 Generated with Claude Code

Cut: merged-on-next only (2026-10-24)

Sean approved the cut list and asked to keep the agents/capabilities vision line.

This commit updates the 2.0 announcement cards and breaking-change lines so they match work merged on next.

Kept as vision:

• Relstrip / lede / h2: "the integration backend for people and their agents"
• One sentence under the h2 that typed capabilities for agents are in review
• Base-branch lines about agents/capabilities (outside this PR's prior diff) left alone

Cut: defineIntegration / documents / workflows cards, Mgmt API v2 / proxy / scopes, two app profiles, fail-closed / osls 4 / Netlify host claims, and the "We run it ourselves" dogfood block.

  

[cursor]

Group 5 review (release-day announcement) — COMMENT only · do NOT merge

Copy-only review as instructed. This stays a draft until npm view @friggframework/core dist-tags.latest is 2.0.1 and the features the cards claim are actually on next / published. Do not merge on release day if #660’s open dependency list is still open.

Would-approve verdict: changes needed (copy accuracy). Same unmerged-feature problem as #660, now on the public homepage.

[cursor]

blocking (copy) — Card states defineIntegration, JSON documents, capability manifests, sync engine, recurring triggers, and dry runs as shipping in 2.0. None of that is on next (#669 / #692–#700 open). Same overclaim pattern as #660.

Failure scenario: Homepage merges on release day while those PRs are still open → public site tells adopters to call defineIntegration / publish definition documents → APIs do not exist in the published package.

[cursor]

blocking (copy) — “Every deployed stage encrypts, dev included”, frigg validate, and osls 4 are listed as shipping. On next: encryption still bypasses dev/test/local (#663 open), there is no frigg validate command (#666 open), and osls is still ^3.78.0 (#664 open).

Failure scenario: Adopter upgrades because the homepage says encryption fails closed and frigg validate runs on every deploy → neither behavior exists yet → false security/ops expectations.

[cursor]

blocking (copy) — Presents Management API v2 (/api/v2), adopter-token auth, organization memberships, entity scopes, and the entity proxy as current 2.0 features. General Management API v2 / proxy / scopes stacks are still open on next (#671, #678, #681–#685, #690).

Failure scenario: Release-day homepage tells agents to use GET /api/meta and POST /api/v2/entities/:id/proxy → routes/config absent in the published build → agent integrations fail against the documented API.

[cursor]

blocking (copy) — “Set provider: 'netlify' and the same app runs on Netlify Functions.” Netlify provider (#686) and ADR-028 register work (#644) are still open; next has no working provider: 'netlify' deploy path.

Failure scenario: Reader sets provider: 'netlify' after seeing this card → build/deploy ignores or errors on the key → “more than one host” promise on the homepage is false.

[cursor]

blocking (process/copy) — Strip says “Frigg 2.0.1 is out” and the hero chip says “out now”. Correct for release day only. Merging while latest is not 2.0.1, or while #660’s open dependency list remains open, publishes a false release announcement.

Failure scenario: Draft is marked ready / merged before npm latest is 2.0.1 → public site claims the release is out → install ^2.0.1 fails or resolves incorrectly; reinforce: keep draft, do not merge (especially not before the docs/deps gate).

[cursor]

should-fix — Hero lede / #v2 framing is fine for release day, but the page <meta name="description"> (unchanged from #661 base) still claims every integration “is also an MCP tool” as present tense, while the shift section correctly keeps the Roadmap tag.

Failure scenario: Social/search unfurl overclaims MCP on the same page that announces 2.0.1 as production-ready.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud