chore(deps): bump typescript from 5.9.3 to 6.0.2

[dependabot]

• Reproduce the reported lint/test/build failure locally and inspect CI context
• Identify the minimal code change needed to fix the TypeScript 6 type-check error
• Run targeted validation (type-check/build and relevant tests)
• Run final validation checks and address any findings
• Reply to the PR comment with the fixing commit hash

[dependabot]

Labels

The following labels could not be found: dependencies. Please create it before Dependabot can add it to a pull request.

Please fix the above issues or remove invalid values from dependabot.yml.

[Copilot]

Pull request overview

This PR upgrades the repository’s TypeScript toolchain to TypeScript 6.0.2, updating the root dependency and aligning the lockfile’s resolved TypeScript and TypeScript-ESLint ecosystem versions accordingly.

Changes:

• Bump typescript from 5.9.3 to 6.0.2 in package.json.
• Update package-lock.json to resolve typescript@6.0.2 and newer @typescript-eslint/* / typescript-eslint transitive versions compatible with TS 6.

Reviewed changes

Copilot reviewed 1 out of 2 changed files in this pull request and generated no comments.

File	Description
package.json	Updates the pinned TypeScript devDependency to 6.0.2.
package-lock.json	Updates resolved dependency graph for TypeScript 6.0.2 and related lint tooling packages.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[tangshixiang]

please fix the lint-test-build error :

innoclaw@0.2.0 prebuild
node scripts/check-deps.js

innoclaw@0.2.0 build
next build

⚠ No build cache found. Please configure build caching for faster rebuilds. Read more: https://nextjs.org/docs/messages/no-cache
▲ Next.js 16.2.2 (Turbopack)

Creating an optimized production build ...
Turbopack build encountered 2 warnings:
./next.config.ts
Encountered unexpected file in NFT list
A file was traced that indicates that the whole project was traced unintentionally. Somewhere in the import trace below, there are:

• filesystem operations (like path.join, path.resolve or fs.readFile), or
• very dynamic requires (like require('./' + foo)).
  To resolve this, you can
• remove them if possible, or
• only use them in development, or
• make sure they are statically scoped to some subfolder: path.join(process.cwd(), 'data', bar), or
• add ignore comments: path.join(/turbopackIgnore: true/ process.cwd(), bar)

Import trace:
App Route:
./next.config.ts
./src/app/api/git/clone/route.ts

./next.config.ts
Encountered unexpected file in NFT list
A file was traced that indicates that the whole project was traced unintentionally. Somewhere in the import trace below, there are:

• filesystem operations (like path.join, path.resolve or fs.readFile), or
• very dynamic requires (like require('./' + foo)).
  To resolve this, you can
• remove them if possible, or
• only use them in development, or
• make sure they are statically scoped to some subfolder: path.join(process.cwd(), 'data', bar), or
• add ignore comments: path.join(/turbopackIgnore: true/ process.cwd(), bar)

Output asset trace:
[output]/.next/server/instrumentation.js
[output]/.next/server/chunks/[root-of-the-server]__0o9arjp._.js

Import trace:
App Route:
./next.config.ts
./src/app/api/git/clone/route.ts

✓ Compiled successfully in 15.3s
Running TypeScript ...
Failed to type check.

./src/lib/deep-research/memory-fabric.ts:231:10
Type error: Right operand of ?? is unreachable because the left operand is never nullish.

229 | ...(checkpoint?.openQuestions ?? []),
230 | ...((claimMap?.gaps ?? []).map((gap) => gap.topic)),

231 | ...((review?.literatureGaps ?? []) ?? []),
| ^
232 | ]).slice(0, 8);
233 |
234 | const activeHypotheses = dedupeStrings([
Next.js build worker exited with code: 1 and signal: null
Error: Process completed with exit code 1. @copilot

[Copilot]

please fix the lint-test-build error :

innoclaw@0.2.0 prebuild
...

Fixed in commit 39c66e2. I removed the redundant nullish-coalescing fallbacks in src/lib/deep-research/memory-fabric.ts that TypeScript 6 flags as unreachable, which resolves the reported type-check/build failure.

Warning

Firewall rules blocked me from connecting to one or more addresses (expand for details)

I tried to connect to the following addresses, but was blocked by firewall rules:

• registry.npmmirror.com
  • Triggering command: /home/REDACTED/work/_temp/ghcca-node/node/bin/node node /home/REDACTED/work/_temp/ghcca-node/node/bin/npm install --ignore-scripts (dns block)

If you need me to access, download, or install something from one of these locations, you can either:

• Configure Actions setup steps to set up my environment, which run before the firewall is enabled
• Add the appropriate URLs or hosts to the custom allowlist in this repository's Copilot coding agent settings (admins only)