docs(site): clarify DomainKit positioning

[aryasaatvik]

Summary

• clarify DomainKit's provider-independent DNS setup positioning across the homepage and README
• tighten provider, registry, and workshop copy around the same product vocabulary
• replace the docs site's green accent with the restrained blue accent used by the current site direction
• add a product-marketing guardrail for future documentation work

Surface	Positioning
Homepage	Domain setup infrastructure for SaaS
Provider docs	Authorization and DNS operations without provider-specific product UI
Workshop	Real package components and fake transport for safe flow exploration

Validation

• isolated 28-page docs build
• registry example check
• public reference check
• core package build
• repository lint, format, and diff checks

The already-running docs development server was left untouched.

[github-actions]

Tegami

This repository uses Tegami to manage releases. When your changes affect published packages, add a changelog file under .tegami/ before merging.

Create a changelog → · Changelog format

Release preview

Package	Bump	Version
domainkit	minor	0.3.1 → 0.4.0
@domainkit/react	minor	0.3.1 → 0.4.0

This PR does not add changelog files. Pending changelogs from other branches are included in the preview above.

Run bun run tegami locally to create a changelog interactively.

_{Managed by Tegami.}

[greptile-apps]

Greptile Summary

The PR revises DomainKit’s public positioning, provider guides, homepage presentation, workshop wording, and registry example. The Cloudflare guide’s corrected observation flow still cannot reliably reconstruct account-token providers from persisted Promise API data.

• Clarifies the host-owned product and security boundary across the README and docs.
• Expands Cloudflare and Vercel connection guidance and provider reconstruction examples.
• Updates homepage provider branding, registry marks, and the site accent color.

Confidence Score: 4/5

The PR is not yet safe to merge because the Cloudflare Promise guide cannot reliably reconstruct an account-token provider for the corrected observation flow.

The persisted Cloudflare provider context wraps tokenKind inside a generic envelope, while the guide reads a decoded field without an exported Promise-facing provider-context decoder; account tokens can consequently be reconstructed with user-token behavior and fail authentication.

Files Needing Attention: apps/docs/content/providers/cloudflare.mdx

Important Files Changed

Filename	Overview
apps/docs/content/providers/cloudflare.mdx	Fixes the previously reported Promise verification example issues, but the reconstruction step lacks a usable Promise-facing decode path for Cloudflare token context.
apps/docs/content/providers/vercel.mdx	Expands Vercel installation, token, reconstruction, and zone-discovery guidance without an accepted blocking issue.
apps/docs/content/index.mdx	Reframes the overview around provider-connected domain setup and explicitly documents host versus library responsibilities.
apps/docs/pages/index.astro	Updates homepage positioning and adds provider marks to the capability presentation.
.agents/product-marketing.md	Adds product-positioning, claim-boundary, terminology, and evidence guardrails for future documentation work.

_{Reviews (11): Last reviewed commit: "docs(marketing): approve frictionless an..." | Re-trigger Greptile}

Dismissed because a newer commit was pushed; Greptile will re-review the current head.

Dismissed because a newer commit was pushed; Greptile will re-review the current head.

Dismissed because a newer commit was pushed; Greptile will re-review the current head.

Dismissed because a newer commit was pushed; Greptile will re-review the current head.

[greptile-apps]

Provider context cannot be decoded

When a Promise API reader reconstructs an account-token provider from the persisted context, context.tokenKind is unavailable because the stored value is an envelope and the Promise facade exposes no provider-specific decoder. Reading the envelope directly either fails type checking or passes undefined, selecting the user-token verification endpoint and causing account-token authentication to fail.

Knowledge Base Used:

• Cloudflare and Vercel authentication
• Promise API integration