Collapse the start surface to one path and one first move

What does this MR do and why?

/start/ is now the adopt page: the bundle URL as the first content, the agent-flow figure, the harness list, and one-line pointers to the pipeline standard and the templates. /start/adopt/ is deleted, the chooser it hung off is gone, and the home page loses its capability card grid, which rendered the sidebar a second time as a menu. The consumption-tier table leaves too; its two survivors, narrower scope per standard and the link index, were already stated one screen above. README.md's ## How to use it opens with the same URL the site opens with, and ## Adoption is deleted, its second step having pointed at a /fleet/ page the site does not publish.

References

Closes #7 (closed)

Standards affected

None. No standards/ directory changes, no check.sh changed, and just sync moves no ## Verify block. standards/presentation/check.sh reads README.md for the H1, hero embed, badge, footer, wordmarks, and compliance pointer; none of those lines change.

Exemption implications

None.

Test plan

  • just guard passes locally
  • just check and just check REPO=. pass locally (self-conformance)
  • just build && just agent succeeds (full pre-deploy gate, run as just ship); just validate-agent-surface agrees sections.ts with STATIC_PAGES after the route removal
  • No standards/<name>/check.sh changed, so no consumer run applies
  • templates/ unchanged
  • design/ unchanged; the built site was checked by grep: /start/adopt/ is absent from dist/, llms.txt, and llms-full.txt, and /start/index.html carries the bundle URL and the .agent-flow figure

Reviewer checklist

  • Voice is GitLab Inc. neutral (no solo-developer narrative, no decorative essays)
  • No em-dashes in customer-facing prose
  • No filler words ("comprehensive", "robust", "leverage", "seamless")
  • Trailers present (Signed-off-by:, Changelog: if user-visible, AI-Assisted:/AI-Tools: if applicable)
  • CODEOWNERS section matches paths touched
  • If breaking for consumers, CHANGELOG entry calls it out and the schedule is realistic

Merge request reports

Loading
Loading