chore(deps): bump n3 from 2.2.0 to 2.7.12

[dependabot]

Bumps n3 from 2.2.0 to 2.7.12.

Release notes

Sourced from n3's releases.

v2.7.12

2.7.12 (2026-09-06)

Bug Fixes

• lexer: report precise reusable source ranges (#721) (fa82a61)

v2.7.11

2.7.11 (2026-09-06)

Performance Improvements

• lexer: avoid match arrays for fixed tokens (#729) (0777d2e)

v2.7.10

2.7.10 (2026-09-06)

Performance Improvements

• lexer: dispatch separators by character (#727) (73b38b3)

v2.7.9

2.7.9 (2026-09-05)

Performance Improvements

• lexer: identify literal delimiters with direct checks (#728) (824bdaf)

v2.7.8

2.7.8 (2026-09-05)

Performance Improvements

• lexer: recognize direction markers without regex matching (#726) (e4e2148)

v2.7.7

2.7.7 (2026-09-05)

Bug Fixes

• stream-parser: initialize the readable object-mode buffer (#723) (4607e09), closes hi#water

v2.7.6

2.7.6 (2026-09-05)

... (truncated)

Commits

• fa82a61 fix(lexer): report precise reusable source ranges (#721)
• 0777d2e perf(lexer): avoid match arrays for fixed tokens (#729)
• 73b38b3 perf(lexer): dispatch separators by character (#727)
• 824bdaf perf(lexer): identify literal delimiters with direct checks (#728)
• e4e2148 perf(lexer): recognize direction markers without regex matching (#726)
• 4607e09 fix(stream-parser): initialize the readable object-mode buffer (#723)
• 10f78e4 perf(lexer): skip unescaping strings without backslashes (#725)
• 4788065 fix(stream-parser): respect backpressure when importing readable streams (#724)
• 10eafd3 fix(lexer): ignore stale callbacks after reuse (#722)
• 8585618 fix(store): handle deletions during iteration (#720)
• Additional commits viewable 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)

[davidwkeith]

Reviewed against CONTRIBUTING.md. This is a routine Dependabot bump (n3 2.2.0 → 2.7.12 in packages/rdf), and it looks fine to merge:

• Diff scope: only packages/rdf/package.json and pnpm-lock.yaml change — no code edits, consistent with a pure dependency bump.
• Changeset: none included, but that matches precedent — the prior n3 bump (#485, 2.1.1 → 2.2.0) also merged without a changeset, and CONTRIBUTING.md only requires one for a "user-visible change to a publishable package," which a dependency patch isn't treated as here.
• PR title: chore(deps): bump n3 from 2.2.0 to 2.7.12 uses Dependabot's default deps scope rather than the repo convention of scoping to the touched package (rdf). Strictly per CONTRIBUTING.md §6 this would read as chore(rdf): …, but every prior automated dependency PR in history (#485, #493, #495, #494, etc.) was merged with the same chore(deps): …/chore(deps-dev): … pattern, so this isn't a new deviation — flagging only for awareness, not requesting a change.
• PR body/template: doesn't follow .github/PULL_REQUEST_TEMPLATE.md's Summary/Packages affected/Checklist headings, but again this is Dependabot's standard body and matches how every previous dependency-bump PR in this repo has looked — not something to fix here.
• Compatibility: the N3.js 2.2.0→2.7.12 range (per the linked release notes) is bug-fix/perf-only (lexer fixes, stream-parser backpressure, store iteration-during-delete fix) with no breaking API changes called out, and @dwk/rdf only consumes N3.js's stable parse/write surface, so no spec or code changes are needed on this side.
• CI: release-gate, integration, and CodeQL are green as of this review; build-test (the lint→format→typecheck→build→test gate) was still running — worth confirming it finishes green before merging.

No changes requested.

---

Generated by Claude Code