chore(deps-dev): bump brace-expansion from 5.0.9 to 5.0.12

[dependabot]

Bumps brace-expansion from 5.0.9 to 5.0.12.

Commits

• f341015 5.0.12
• 33a5ef1 Merge commit from fork
• 8247927 5.0.11
• 935d78f Merge commit from fork
• df7682f 5.0.10
• 1ade9de npm run format
• 6735c94 Merge commit from fork
• 4e70465 chore: ensure prettier formatting (#154)
• fd7a5e3 Bump ip-address from 10.2.0 to 10.4.0 (#152)
• 1790143 Bump uuid and @​tapjs/processinfo (#120)
• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
  You can disable automated security fix PRs for this repo from the Security Alerts page.

[claude]

Reviewed. Lockfile-only change, no findings.

• The single brace-expansion entry in package-lock.json moves 5.0.9 to 5.0.12 and stays "dev": true, so nothing reaches the published runtime dependency tree.
• The bumped version satisfies the only declared requirement in the tree (minimatch@10.2.6 requires brace-expansion: ^5.0.8), and its balanced-match: ^4.0.2 dependency is already satisfied by the locked balanced-match@4.0.4.
• resolved and integrity are updated together, and engines is unchanged (20 or >=22), so the .nvmrc 24.13.0 and Node 22 CI matrix are unaffected.
• No package.json change, so the exact-pin rule for playwright and the release-contract tests are untouched.

Nothing here touches source, so the explicit sessionId and pageId addressing, context isolation, per-session serialization, and log-leak contracts do not come into play, and there is no new behaviour to cover with tests.