Sync nextjs examples to @arkenv/nextjs 0.1.6

[yamcodes]

Description

Restores examples sync after the @arkenv/nextjs 0.1.6 version bump from Version Packages (#1841).

pnpm sync:examples updated:

• examples/with-nextjs and examples/with-nextjs-strict package.json (@arkenv/nextjs: ^0.1.5 → ^0.1.6)
• matching package-lock.json files for those examples

This fixes the failing check-sync job on the Sync dev → main workflow.

Verified: pnpm sync:examples:check exits 0.

Type of Change

• Bug fix (non-breaking change which fixes an issue)

Checklist

• My code follows the code style of this project (double quotes, tabs, no parameter reassignment).
• I have written sentence-case imperative commits / PR title (e.g. Add support for custom error messages - no feat:, no trailing period, capitalized).
• I have added tests to cover my changes.
• All new and existing tests passed.
• I have created a changeset using pnpm changeset (if this affects a published package).

For v0 (dev) PRs:

• Forward-Porting: (For maintainers) Has this change been manually forward-ported to the v1 branch?

No changeset needed — examples-only sync, no published package source changes.

sync-examples-check.log

_{To show artifacts inline, enable in settings.}

  

[changeset-bot]

⚠️ No Changeset found

Latest commit: cdb8895

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 no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

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

[pullfrog]

✅ No new issues found.

Reviewed changes — Single commit bumping @arkenv/nextjs ^0.1.5 → ^0.1.6 in examples/with-nextjs and examples/with-nextjs-strict, regenerating both package-lock.json files to match.

• @arkenv/nextjs manifest bump — ^0.1.5 → ^0.1.6 in both example package.json files, restoring sync:examples:check parity after the 0.1.6 publish.
• Lockfile regeneration — both lockfiles now resolve @arkenv/nextjs 0.1.6 (with chokidar@^5.0.0 + the nested chokidar@5.0.0/readdirp node and the widened react peer range as they appear in the published 0.1.6 metadata), plus incidental next/@next/* 16.3.x and libc-field churn from the npm regen.

Verified directly: @arkenv/nextjs@0.1.6 exists on the registry with exactly the chokidar/react metadata recorded in the regenerated lockfiles; pnpm sync:examples:check exits 0 in this workspace; and no other example or playground references @arkenv/nextjs at a stale version. Lockfile root dependency blocks now match the manifests.

  ^{｜ View workflow run ｜ Using DeepSeek Flash (free via Pullfrog for OSS) ｜ 𝕏}