Legacy identifiers note, softened REST claim, llms.txt legacy line

[next-devin]

Follow-up to #32. Three wording changes that needed the product owner's call, now made.

What

• Legacy identifiers, in plain words. A "Why 29next?" callout on Get Started, the first page where a merchant meets accounts.29next.com: Next Commerce was formerly 29 Next; the account and store hostnames, API headers, and API key namespace still carry that name; they are current on every store and not scheduled to change. A clean agent evaluation on 2026-09-03 answered "is 29Next a different company?" only from a marketing-site banner, and a second run could not answer it at all from the docs sites.
• About page: "The platform's core capabilities are accessible through well-documented REST APIs" instead of "Every capability". Agents read the absolute literally and check it.
• /llms.txt: the same legacy-identifiers sentence in the header, so an agent that never reaches Get Started still sees it.

Verified

• npm run build including the link audits, search index budget check passes. The callout and the About wording render in out/.

Decision needed from — none; these were Alex's answers.

Sibling PR on developer-docs carries the developer-side changes (Spark as starter theme, Theme Kit links, disputes and campaign-order notes, reference-URL redirect).

🤖 Generated with Claude Code

[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	nextcommerce-docs	dc1c2b3	Commit Preview URL Branch Preview URL	Sep 03 2026, 09:15 AM

[kilo-code-bot]

Code Review Summary

Status: No Issues Found | Recommendation: Merge

Both prior issues on content/docs/start-here/get-started/index.mdx are resolved by the follow-up commit dc1c2b3:

• The redundant import { Callout } from 'fumadocs-ui/components/callout'; has been dropped, restoring consistency with the rest of content/docs/.
• The store hostname placeholder is now rendered as `your-store.29next.store`, where `your-store` is your store's own name, providing the visual and textual gloss previously requested.

No new issues were introduced in the changed lines.

Files Reviewed (1 file in incremental diff)

• content/docs/start-here/get-started/index.mdx - 0 new issues (2 prior issues resolved)

Previous Review Summary (commit e419aca)

Current summary above is authoritative. Previous snapshots are kept for context only.

Previous review (commit e419aca)

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/docs/start-here/get-started/index.mdx	5	Explicit Callout import is inconsistent with every other mdx file in content/docs/, which rely on the global MDX components mapping.

SUGGESTION

File	Line	Issue
content/docs/start-here/get-started/index.mdx	14	{store}.29next.store is a template rendered as prose; could be misread as a literal hostname by merchants or agents.

Files Reviewed (3 files)

• app/llms.txt/route.ts - 0 issues
• content/docs/about-next.mdx - 0 issues
• content/docs/start-here/get-started/index.mdx - 2 issues

Fix these issues in Kilo Cloud

---

_{Reviewed by minimax-m3 · Input: 25.2K · Output: 1.7K · Cached: 86.5K}