chore(deps-dev): bump the dev-dependencies group across 1 directory with 3 updates

[dependabot]

Bumps the dev-dependencies group with 3 updates in the / directory: @blackwell-systems/gcf, @toon-format/toon and @types/node.

Updates @blackwell-systems/gcf from 2.4.0 to 2.5.2

Release notes

Sourced from @​blackwell-systems/gcf's releases.

v2.5.2

• Score rounding fix (SPEC 5, spec v3.5.1 errata). The graph node-line score now rounds half-to-even on the exact IEEE-754 double, matching the Go/Rust/Python/Swift/.NET reference. The previous Number.prototype.toFixed formatter rounded half-up, so it diverged at exact binary midpoints (0.125 -> 0.13 instead of 0.12, 0.625 -> 0.63 instead of 0.62) - a silent, non-interoperable wire difference. Pinned by the new graph-encode/004_score_midpoint_rounding conformance fixture. Encoding is unchanged for every non-midpoint score.

Part of spec v3.5.1.

v2.5.1

Decoders now reject a declared section count ([N]) that does not match the actual number of items, in both directions, per SPEC Section 13 (Count Validation). A declared count smaller than the items present was previously treated as a read limit and the surplus was dropped; it is now an error. This applies to the generic tabular, keyed-map, and root-array forms, the delta and full-set decoders, and the graph edge section.

Valid payloads are unaffected and encoding is unchanged: encoders always emit accurate counts, so this only changes how malformed or externally produced input is handled, rejecting it rather than silently truncating. New shared conformance fixtures pin the behavior in both directions.

v2.5.0: Keyed-tabular map encoding

Keyed-tabular map encoding (GCF spec v3.5.0).

Highlights

Keyed-tabular map encoding (SPEC §7.2a). A JSON object whose values are all objects forming a tabular set now encodes as a keyed table: the shared value fields are declared once in a header, with one key-prefixed row per member (## [N:]{key,...}). It is canonical by default, works in nested and streaming positions, and reuses generic delta with the map key as the identity, so an object-of-objects that recurs across an agent loop sends only what changed.

Also in this release

• Negative zero canonicalizes to 0 for both integer and floating-point values (SPEC §2.3.1).
• Canonical-output alignment across all six SDKs: object key ordering, graph header fields, and symbol ordering follow the specification and reference implementation exactly.

Compatibility

Additive. Existing payloads are unaffected. A pre-v3.5 decoder rejects the [N:] keyed-map marker, so decoders should be updated to read v3.5 output.

Quality

Verified by the shared cross-language conformance suite (byte-exact across all six SDKs), a re-encode idempotence check on the generic, graph, and delta profiles, and a differential cross-SDK fuzz in which the tree-sitter grammar parses every wire the SDKs emit.

Spec release: https://github.com/blackwell-systems/gcf/releases/tag/v3.5.0

Changelog

Sourced from @​blackwell-systems/gcf's changelog.

v2.5.2 (2026-08-09)

• Score rounding fix (SPEC 5, spec v3.5.1 errata). The graph node-line score now rounds half-to-even on the exact IEEE-754 double, matching the Go/Rust/Python/Swift/.NET reference. The previous Number.prototype.toFixed formatter rounded half-up, so it diverged at exact binary midpoints (0.125 -> 0.13 instead of 0.12, 0.625 -> 0.63 instead of 0.62) - a silent, non-interoperable wire difference. Pinned by the new graph-encode/004_score_midpoint_rounding conformance fixture. Encoding is unchanged for every non-midpoint score.

v2.5.1 (2026-08-07)

• Decoders now reject a declared [N] section count that does not match the actual item count, in both directions, per SPEC Section 13 (Count Validation). A declared count smaller than the rows or entries present was previously read as a limit and the surplus was dropped; it is now an error. Covers the generic tabular, keyed-map, and root-array forms, the delta and full-set decoders, and the graph ## edges [N] section. Valid payloads and encoding are unchanged.

v2.5.0 (2026-08-07)

Added

• Keyed-tabular map encoding (SPEC 7.2a): a JSON object whose values are all objects forming a tabular set is encoded as a keyed table (## [N:]{key,...}) - the shared value fields are declared once, with one key-prefixed row per member. Canonical by default, supported in nested and streaming positions, and integrated with generic delta using the map key as the identity.

Changed

• Negative zero is canonicalized to 0 for both integer and floating-point values (SPEC 2.3.1).
• Canonical-output alignment across all six SDKs: object key ordering, graph header fields, and symbol ordering follow the specification and reference implementation exactly.

Testing

• Conformance runners assert re-encode idempotence (encode(decode(x)) == x) for the generic, graph, and delta profiles; a differential cross-SDK fuzz was added to the verification suite.

Commits

• 4a440ce release: v2.5.2 — score rounding half-to-even (spec v3.5.1 errata)
• 715f5f9 fix: round graph score half-to-even to match the reference (SPEC 5)
• 82aa33f docs: update version references (spec v3.5.0, v2.5.1 / Go v1.6.1 / Swift v2.6...
• 929f849 fix: enforce declared [N] section counts in both directions (SPEC 13)
• 53df904 docs: absolute README image/LICENSE URLs for guaranteed npm page rendering
• 6b71173 chore: bump to 2.5.0
• d7e849a conformance: assert graph + generic-delta re-encode idempotence
• 46ad9a1 encode: canonicalize negative zero to 0 (SPEC 2.3.1)
• 7b161ac decode: preserve object field order (Map-based reconstruction)
• ae21ad2 generic: preserve first-observed object key order via order-preserving parse
• Additional commits viewable in compare view

Updates @toon-format/toon from 4.1.0 to 4.1.1

Release notes

Sourced from @​toon-format/toon's releases.

v4.1.1

   🐞 Bug Fixes

• Write CLI diagnostics to stderr so stdout carries results only  -  by @​johannschopplich (46757)
• Terminate the last line of file output with a newline  -  by @​johannschopplich (c3d7c)
• Treat a tab-indented hash line as content, not a comment  -  by @​johannschopplich (6e822)
• Reject a raw string whose comment marker follows a byte-order mark  -  by @​johannschopplich (bde6e)

    View changes on GitHub

Commits

• a9e6d97 chore: release v4.1.1
• 349941c chore: update @​toon-format/spec to v4.1.1
• bfca235 docs: list the misplaced scalar line among the both-mode decode errors
• bde6eae fix: reject a raw string whose comment marker follows a byte-order mark
• 6e822b3 fix: treat a tab-indented hash line as content, not a comment
• 1ab9e43 style: trim package and docs comments to intent and constraints
• 0d9945b style: mark benchmark question sections with regions
• c702deb style: trim benchmark comments to intent and constraints
• 96c53e5 style: open shared boundary docs with a verb and name values as nouns
• 05adaf3 build: update the lockfile after dropping the runtime dependencies
• Additional commits viewable in compare view

Updates @types/node from 26.1.2 to 26.2.0

Commits

• See full diff in compare view