docs: update Yutori integration to Navigator n1.5

[dprevoznik]

Summary

Reflects the CLI's v0.19.1 Yutori template upgrade in the docs:

• Integration page (integrations/computer-use/yutori.mdx) now references Navigator n1.5 instead of n1, and links to the n1.5 blog post and API docs.
• Integrations overview entry updated to "Yutori Navigator n1.5".

Test plan

• Preview renders cleanly on Mintlify
• Links resolve (yutori.com/blog/introducing-n1-5, docs.yutori.com/reference/n1-5)

[mintlify]

Preview deployment for your docs. Learn more about Mintlify Previews.

Project	Status	Preview	Updated (UTC)
Kernel	🟢 Ready	View Preview	May 13, 2026, 8:32 PM

💡 Tip: Enable Workflows to automatically generate PRs for you.

[firetiger-agent]

Firetiger deploy monitoring skipped

This PR didn't match the auto-monitor filter configured on your GitHub connection:

Any PR that changes the kernel API. Monitor changes to API endpoints (packages/api/cmd/api/) and Temporal workflows (packages/api/lib/temporal) in the kernel repo

Reason: PR only updates documentation (integrations page, overview entry, and changelog) with no changes to API endpoints or Temporal workflows.

To monitor this PR anyway, reply with @firetiger monitor this.

[cursor]

Risk assessment: Very Low.

I reviewed the actual diff only. This PR changes three .mdx documentation files: adds a changelog entry, updates the Yutori integration page from n1 to Navigator n1.5, and updates one integration overview description. There are no code, config, prompt, navigation, auth, infra, or schema changes, and I found no CODEOWNERS file requiring an owner review. The PR also has no existing approvals, so approval is appropriate for this risk level.

  

_{Sent by Cursor Automation: Assign PR reviewers}

[cursor]

Risk assessment: Very Low.

I reviewed the current diff only. The synchronized PR now changes two .mdx documentation files: the Yutori integration page and the integrations overview entry. The edits update product naming from n1 to Navigator n1.5 plus related documentation/blog links. There are no code, config, navigation, prompt-instruction, auth, infra, schema, or runtime behavior changes, and I found no CODEOWNERS file requiring owner review.

The PR is already approved, so I’m not adding a duplicate approval. The updated diff does not increase risk from the prior assessment.

  

_{Sent by Cursor Automation: Assign PR reviewers}