docs: promote Apps above Core Architecture, rewrite Templates doc

[kapunahelewong]

What changed

Nav reorg (docsNavItems.ts)

• The "Apps" section (all per-app doc groups: Chat, Mail, Calendar, Content, Brain, Assets, Slides, Analytics, Clips, Design, Forms, Plan, Dispatch) previously sat at the very bottom of the docs sidebar, below Toolkit and Advanced Runtime. Moved it to sit right after Overview, above Core Architecture.
• cloneable-saas.mdx (Templates) and pure-agent-apps.mdx (Automation-First Apps) moved out of the Overview section into this same Apps section, as its first two items — they already cross-link each other as the two app archetypes (full-UI template vs. no-browser-UI automation), so they now sit with the catalog they introduce instead of being orphaned pages under Overview.
• No slug/URL changes — this is a sidebar-order and section-membership change only.

Content rewrite (cloneable-saas.mdx)

• Reframed the opening to state the two app archetypes directly and reworked the "see the full catalog" pointer, which used to link to a separate hosted-app gallery route under a confusingly similar name — it now correctly distinguishes the sidebar docs group from the hosted gallery at /apps.
• Full tone pass for clarity and concision: cut marketing language ("Agent-native flips that", "SaaS-grade", "superpowers", stacked rhetorical questions, repeated "already X, already Y" emphasis) in favor of direct statements. Fixed a sentence that referenced "the docs in the sidebar below it" — nav-position-dependent phrasing that breaks if the nav changes — with wording that just states what the doc covers and links to the sibling doc for the other archetype.
• Left the Community Templates section and the per-app catalog table mostly untouched — both were already factual/technical, not marketing-toned.
• Did not rename the page's own title/H1 away from "Templates" — that title is referenced by name from 30+ other English docs pages (×10 locales), so renaming it is a separate, larger sweep outside this PR's scope.

Verification

• oxfmt --check clean on both changed files.
• tsc --noEmit clean in packages/docs.
• Full packages/docs test suite passes (28 files, 162 tests), including templates-routes.test.ts, which specifically asserts the "Apps" section stays wired to the featured template catalog.
• Full pnpm guards suite passes.
• Loaded the docs dev server locally and confirmed the new sidebar order renders correctly with all app groups intact (no content lost or duplicated in the move) and the rewritten page copy reads cleanly.

Notes for reviewers

• The docsNavItems.ts diff is large in line count (~1200 lines) because moving a ~400-line section within the file shows as a delete+add of everything after it — it's a reorder, not a rewrite of the per-app group definitions themselves (those are unchanged).
• Nav item labels (e.g. "Templates" as the label for cloneable-saas) were left as-is to avoid touching the corresponding i18n keys across 10 locale catalogs; only English content changed.

🤖 Generated with Claude Code

[github-actions]

Here's a visual recap of what changed:

Open the full interactive recap

[builder-io-integration]

Builder reviewed your changes — looks good ✅

Review Details

Incremental Code Review Summary

I reviewed the current PR #2786 head and confirmed it matches the state covered by the prior review: the Apps sidebar reorder, English Templates rewrite, ten localized MDX rewrites, and the core patch changeset. The latest code-review passes found no new delta requiring additional feedback; navigation metadata, localized frontmatter, docs links, and changeset structure remain valid.

Risk assessment: Low. The PR is limited to documentation content, localization, navigation configuration, and release metadata. It does not alter backend behavior, APIs, authentication, data access, or runtime logic. No previous findings require resolution.

Key Findings

No actionable findings.

✅ Current HEAD is consistent with the previously reviewed documentation changes.
✅ All affected docs routes and localized pages remain reachable in HTTP-level checks.
✅ Intended sidebar ordering and navigation slugs remain intact.

🧪 Browser testing: Skipped — browser automation tools were unavailable in this session. The docs server and affected routes were reachable, but interactive visual evidence could not be captured.

[steve8708]

thanks @kapunahelewong!