build(deps-dev)(deps-dev): Bump the development-dependencies group with 2 updates

[dependabot]

Bumps the development-dependencies group with 2 updates: @types/node and fallow.

Updates @types/node from 26.1.2 to 26.2.0

Commits

• See full diff in compare view

Updates fallow from 3.14.0 to 3.15.0

Release notes

Sourced from fallow's releases.

v3.15.0: near-miss clone detection, diagnosable threshold overrides, community bug fixes

Highlights

Near-miss clone detection and smarter duplicate triage

fallow dupes --near (config duplicates.near) now also detects function-scoped clones with small structural edits, reported with a similarity score. Every clone-group finding carries a new spread field, and --top ranking boosts clones scattered across distant files above local ones, so the duplicates worth consolidating first rise to the top. A new duplicates.ignoredClones list ("dup:<fingerprint>:<instance_count>") silences clone groups a reviewer has accepted; fingerprints hash the normalized token sequence, so formatting-only edits keep a reviewed clone recognized.

Threshold overrides are finally diagnosable (health schema 10)

A health.thresholdOverrides entry that did not silence a finding now tells you why: every override row carries a required dimension (complexity or crap), a new insufficient status marks an override that raises a ceiling the code still exceeds, and an optional outstanding[] lists the dimensions a matched unit still breaches. Overrides now also apply to synthetic \<template> findings in Svelte, Vue, and Astro single-file components, and those findings get a framework-correct suppression hint (<!-- fallow-ignore-next-line complexity --> on the line above the reported line) instead of Angular decorator advice. A follow-up pass made the override rows agree with their findings everywhere: the <component> rollup consults the override resolver, outstanding no longer swaps dimensions between same-named units, status is scored across ceilings, and CodeClimate plus GitHub annotations quote the effective threshold instead of the run-global one. Standalone health and combined output move to schema_version 10; audit output does not embed the health contract and stays at 9. Thanks @​lcestou for the report.

Bug fixes

• Type-aware analysis respects an explicit "private-type-leaks": "off". Enabling typeAware force-enabled the opt-in rule regardless of config, which also made the api-surface sidecar capability mandatory. The explicit setting now wins; unset configs keep the default-on behavior. Thanks @​thewirv.
• cacheMaxAgeDays and FALLOW_AUDIT_CACHE_MAX_AGE_DAYS actually reclaim audit caches now. The base-snapshot cache GC only visited entries under the current repo's hash prefix, so caches from linked worktrees accumulated forever. Abandoned entries from other repo identities now age out, live owners are skipped (a repo's own 0 cannot be defeated from outside), and invalid env values warn instead of silently falling back. Thanks @​EvanAgee.
• --gate new-only no longer fails clone-removal refactors. Extracting a shared helper and deleting duplicate instances shifted the clone group's attribution key and made the surviving duplication look introduced. Groups whose instances contain no added line are now demoted to inherited, while a genuinely pasted clone still fails the gate. Thanks @​devmax128.
• Framework template findings show which conditions caused them. A \<template> complexity finding in Vue, Angular, Svelte, or Astro now reports each decision point at its own line and column with the weight it added, so the VS Code inline breakdown and health --complexity-breakdown work in templates too. Thanks @​Ericlm.
• Windows: added-line attribution now sees untracked files. Native backslash paths passed to the untracked-file diff meant every added-line check on an untracked file silently missed on Windows.
• Svelte await-block complexity labels match the source. {#await} / {:then} contributions were labeled if; they now use explicit await and then kinds, including inline then/catch continuations.
• Malformed config shapes fail loud. A malformed extends value, an unknown key in an overrides entry, or an unknown key in an ignoreExports rule now fails config load with a named error instead of silently disabling the rule it was meant to configure. Run fallow config before upgrading to surface rejected shapes ahead of CI.
• Resolver fixes: .js specifiers resolve to declaration-only .d.ts modules; ignoreUnresolvedImports entries with a leading ./ match again; multi-binding re-exports from a missing module produce one finding anchored on the specifier instead of one per binding.
• Plus: fallow --help lists every subcommand again, fallow setup-hooks can no longer duplicate a hand-edited managed block, audit read failures no longer fabricate weakening signals, a malformed pnpm-workspace.yaml warns instead of silently disabling catalog resolution, MCP workspace comma lists work on API-backed tool paths, untrusted values are escaped in github-summary tables, fallow-ignore-next-line inside multi-line block comments anchors correctly, VS Code binary downloads can no longer hang LSP startup, and LSP analysis no longer blocks the dispatch loop.

Performance

Module resolution and graph build got faster: resolve fallback paths reuse the session canonicalize cache, dynamic-import pattern matching memoizes compiled glob matchers, and reference attachment on high-fan-in modules replaces two quadratic rescans with indexed lookups.

Compatibility

• Health and combined JSON output move to schema_version 10 (required dimension on threshold_overrides[] rows, new insufficient status, optional outstanding[]). Audit output stays at 9.
• Two --format compact health line grammars gained fields (exceeded= on high-complexity:, a dimension segment and optional outstanding= on threshold-override:); key=value consumers are unaffected.
• Three previously-tolerated malformed config shapes are now load errors (see above).
• TypeScript consumers: each output field references its own exact version alias (CheckSchemaVersion, HealthSchemaVersion, ...); the legacy SchemaVersion export remains an alias of CheckSchemaVersion.

Full Changelog: fallow-rs/fallow@v3.14.0...v3.15.0

Commits

• 66ae724 fix(napi): keep the node-binding manifests at the last published version unti...
• 4b48d65 ci: retry the ecosystem project clone (#2206)
• 1c59d2d fix(health): make threshold-override rows agree with their findings (#2207)
• 1e09e51 fix: sync the npm package versions with the 3.15.0 workspace (#2208)
• eaaeb4a chore: release v3.15.0
• 4dadd30 fix(engine): pass forward-slashed paths to the untracked-file diff on Windows
• b204805 chore(deps-dev): bump rolldown from 1.2.0 to 1.2.2 in /viz-frontend (#2181)
• a6848ae test(vscode): pin combined and health envelopes at schema 10 (#2205)
• 54082f0 chore(deps): move the Oxc tooling to oxlint 1.78 and oxfmt 0.63 (#2204)
• 303c667 chore(deps): bump http from 1.4.2 to 1.5.0 (#2187)
• 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 <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions