[stamp-build]

^{AppFather from raft opened this pull request through Stamp
View in Stamp →}

---

Public developer docs for link card buttons that act (#proj-apps:#60, RFC 076 §17). Until now, the action endpoint protocol was shared privately with official App teams. A server-local App can now use acting buttons on its own Server once its admins allow it, so developers need the protocol.

Do not merge before yezizp agrees to opening this to developers, and before the web change (slock #13956) is in production.

What

• New page developers/raft-apps/link-card-actions/ (English), covering:
  • who may use acting buttons;
  • registering action_endpoint and allowing card actions on your own Server (the Card buttons settings section; the permission is for the exact URL, as Tenny decided);
  • execute buttons and client capabilities (unreviewed_app.v1);
  • verifying the signed request (claims, body hash, a jose sketch);
  • answering prepare and execute, terminal updates and status;
  • revisions and stale clicks, limits, refusals, a worked approval example and troubleshooting.
• The link-previews page's "Buttons" paragraph and the Raft Apps overview link to it; sidebar entry added.
• A Chinese mirror is included and passes scripts/zh-cn/check.mjs. Hasaki maintains zh-cn, so please review or take it over (AGENTS.md).

Checks

• Checked the English page against slock staging: the card-action JWT (oidcService.ts signCardActionAssertion), Button limits (appLinkPreview.ts), the eligibility and capability rules (#13940, #13945), the statuses, terminal updates and limits.
• scripts/zh-cn/check.mjs: 0 errors on the new page. Its one error on the Chinese link-previews page is already on main.
• The site wasn't built here (no Node toolchain for VitePress on this host), so anchors and links need CI's build.
• The jose sketch wasn't run.

Requirement Challenge

• Cut: the web client's internal admin routes (not a developer API); internal details (handle signing keys, flags, storage).
• Simplest version: one page with the whole contract, plus links from the two places developers start.
• Constraint owners: Tenny (protocol accuracy), Hasaki (zh-cn), yezizp (launch).

[cloudflare-workers-and-pages]

Deploying raft-docs with    Cloudflare Pages

Latest commit:	d32201b
Status:	✅  Deploy successful!
Preview URL:	https://616b424b.raft-docs.pages.dev
Branch Preview URL:	https://docs-link-card-actions.raft-docs.pages.dev

View logs