[next-devin]

accounts.nextcommerce.com now serves every Nexus account user, so the developer docs stop pointing people at accounts.29next.com.

• Partner registration, app creation and App Kit sign-in steps (server-to-server-apps, storefront-extension, marketing-attribution) link to accounts.nextcommerce.com. The App Kit prompt sample matches the wording in Move app-kit to accounts.nextcommerce.com app-kit#4, which moves nak to the new host.
• The legacy identifiers notice (Admin API intro, AGENTS.md, /llms.txt, and the legacy-identifiers capability record) no longer lists the accounts host. {store}.29next.store and the X-29next-* headers stay as they are because they're platform contract. last_verified on that record is bumped to 2026-10-23 after its two links returned 200.

The docs site's lib/capabilities.snapshot.json picks up the new summary on its next sync-capabilities run after this merges.

[kilo-code-bot]

Code Review Summary

Status: 2 Issues Found | Recommendation: Address before merge

Overview

Severity	Count
CRITICAL	0
WARNING	1
SUGGESTION	1

Issue Details (click to expand)

WARNING

File	Line	Issue
content/capabilities.yaml	433	last_verified bumped to 2026-10-23, but the record's own links (/docs/admin-api, /docs/webhooks) were not re-verified by this PR; the field's documented meaning is a full link check

SUGGESTION

File	Line	Issue
content/docs/apps/guides/storefront-extension.mdx	58	accounts.nextcommerce.com Email: / Password: prompt labels now prefix a non-legacy hostname onto fields nak setup does not ask for; app-kit.mdx calls them simply "Email" / "Password"

Files Reviewed (7 files)

• AGENTS.md - 0 issues
• app/llms.txt/route.ts - 0 issues
• content/capabilities.yaml - 1 issue
• content/docs/admin-api/index.mdx - 0 issues
• content/docs/apps/guides/marketing-attribution.mdx - 0 issues
• content/docs/apps/guides/server-to-server-apps.mdx - 0 issues
• content/docs/apps/guides/storefront-extension.mdx - 1 issue

Verification notes

• No accounts.29next.com references remain anywhere in the repository; the scrub is complete.
• The legacy-identifiers sentence is now identical across all four owners (AGENTS.md:47, app/llms.txt/route.ts:91, content/docs/admin-api/index.mdx:25, content/capabilities.yaml:420), so the four surfaces cannot drift apart in wording.
• lib/generated/capabilities.json is gitignored and regenerated at build time by scripts/generate-capability-map.mjs, so no generated artifact needs committing; last_verified: 2026-10-23 passes the YYYY-MM-DD format and calendar-date validation in source.config.ts:77 and scripts/generate-capability-map.mjs:162.
• Existing live-surface checks remain satisfied: scripts/check-live-surfaces.mjs:231 matches on formerly 29 Next (unchanged) and :232 on the Legacy identifiers heading (unchanged).
• Minor wording nit not commented inline: "store hostnames" is now plural for a single identifier pattern. Cosmetic only.

Fix these issues in Kilo Cloud

---

_{Reviewed by minimax-m3 · Input: 43.4K · Output: 3.3K · Cached: 675.2K}

[cloudflare-workers-and-pages]

Deploying with    Cloudflare Workers

The latest updates on your project. Learn more about integrating Git with Workers.

Status	Name	Latest Commit	Preview URL	Updated (UTC)
✅ Deployment successful! View logs	developer-docs	b7b8a5d	Commit Preview URL Branch Preview URL	Oct 23 2026, 02:22 AM