fix(help): describe the content model in the root help

[angeloashmore]

Resolves: #274

Description

This PR ensures agents have correct knowledge of Prismic's modeling capabilities.

Our evals showed content relationships specifically as a weak point. Instead of linking an author document to a blog post, for example, the agent adds an "Author" key text field.

With this PR, the "models a page type with sensible field types" eval improves from 10/21 total passing runs to 14/15.

Checklist

• If my changes require tests, I added them.
• If my changes affect backward compatibility, it has been discussed.
• If my changes require an update to the CONTRIBUTING.md guide, I updated it.

Preview

$ prismic --help
...
MODELING
  Pages are page types, built from slices and fields. Content that is
  not a page is a custom type, such as an author or a navigation menu.
  A page references a custom type with a content relationship field,
  instead of repeating its content.
  Run `prismic type list` to see what a project has, and
  `prismic docs view content-modeling` for details.

How to QA ¹

$ node --run build
$ node dist/index.mjs --help
$ EVAL_TRIALS=5 PRISMIC_ALLOW_EVALS=true node --run evals -- \
    evals/design-sensible-models.eval.ts evals/check-before-acting.eval.ts

🤖 Generated with Claude Code

https://claude.ai/code/session_01Xywd7QAoQLV7eyGpDvvtMN

---

Note

Low Risk
Help text and a test assertion only; no runtime behavior or API changes.

Overview
Root prismic --help (and default help) now includes a MODELING section alongside existing guidance like ROUTES. The new text explains that pages are page types built from slices and fields, that non-page content lives in custom types, and that pages should link to those types via content relationship fields rather than duplicating data. It also directs users to prismic type list and prismic docs view content-modeling.

The --help integration test is updated to assert MODELING appears in the output.

^{Reviewed by Cursor Bugbot for commit 16703dc. Bugbot is set up for automated code reviews on this repo. Configure here.}

Footnotes

1. Please use these labels when submitting a review:
   ❓ #ask: Ask a question.
   💡 #idea: Suggest an idea.
   ⚠️ #issue: Strongly suggest a change.
   🎉 #nice: Share a compliment. ↩