fix(deps): update dependency nanoid to v6

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
nanoid	^5.0.0 → ^6.0.0

---

Release Notes

ai/nanoid (nanoid)

v6.0.0

Compare Source

• Made nanoid() and customAlphabet() 4 times faster (by @​orhanayd).
• Removed Node.js 18 and 20 support.

v5.1.16

Compare Source

• Fixed forever loop on negative size (by @​spokodev).

v5.1.15

Compare Source

• Fixed random pool corruption on big ID sizes.

v5.1.14

Compare Source

• Fixed npm package size regression.

v5.1.13

Compare Source

• Fixed npm package size regression.

v5.1.12

Compare Source

• Moved to npm Provenance and Staged Publishing.

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • At any time (no schedule defined)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: a1f187736d

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

[chatgpt-codex-connector]

Align draw's supported Node range with nanoid 6

This bump pulls in nanoid 6, whose lockfile now declares "node": "^22 || ^24 || >=26", while the draw package still advertises Node 20.19 support and src/crabcode:8708-8733 only checks that some node binary exists before running npm install. On a supported Node 20.19 setup with engine-strict=true, npm's docs say it will “refuse to install” packages incompatible with the current Node version, so crab draw install can fail for users we still claim to support; either keep nanoid 5 or raise the plugin's Node engine consistently.

Useful? React with 👍 / 👎.