docs: Align optional-shared changeset prose with v1

[yamcodes]

Summary

Align the still-unconsumed #1503 changeset on dev with the consumer-facing prose from the v1 forward-port (#1505). Same packages, bump, title, example, and CLI note — clearer body wording only.

Test plan

• Diff is limited to .changeset/optional-strict-shared.md prose
• Wording matches .changeset/optional-strict-shared-v1.md on the v1 PR

  

[changeset-bot]

⚠️ No Changeset found

Latest commit: bcb450f

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes changesets to release 4 packages

Name	Type
@arkenv/build	Patch
@arkenv/nextjs	Patch
@arkenv/nuxt	Patch
@arkenv/bun-plugin	Patch

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[yamcodes]

LGTM

[pullfrog]

✅ No new issues found.

Reviewed changes — rewords the still-unconsumed optional-strict-shared changeset body and code comment on dev to match the v1 forward-port (#1505). No packages, bump types, heading, or code snippet changed.

• Changeset body rewrite — drops the implementation-detail tone ("Strict layout auto-detection and schema discovery now treat…") for consumer-facing prose ("Strict layout now works with just… Omit internal/shared.ts when you have nothing to share")
• Code comment update — "is valid strict layout" → "is enough"

  ^{｜ View workflow run ｜ Using DeepSeek Pro (free via Pullfrog for OSS) (GPT Sol not used — the program covers this model; add its provider key to run your pick) ｜ 𝕏}