chore: sync upstream v2

[shuv1337]

Summary

• merge 210 upstream V2 commits through a0a6963beb7bc9b613380cb3a608ee887dfdbe1e
• accept upstream's deletion of the legacy V1 package tree
• retain Shuvcode branding, package and binary identities, fork release ordering, and XDG compatibility
• preserve the shared service, QR pairing, device Bearer authentication, mobile capability policy, and loopback attachment support
• regenerate migrations, Effect/Promise clients, and the OpenAPI snapshot against the merged protocol
• keep fork PR CI on Linux while upstream-only management workflows remain disabled here

Validation

• full repository typecheck (pre-push hook): 33/33 packages
• CLI: 157 tests
• TUI: 496 pass, 5 skip
• AI: 395 pass, 29 skip
• focused Core, Server, Client, Protocol, Schema, and Updates suites
• generated-client and migration consistency checks
• native Bun and Node distribution builds with compiled shared-service/pairing lifecycle smoke tests

Downstream ShuvKit, OpenShuv, and ClankerOne contract pins are intentionally not changed in this PR.

[socket-security]

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action	Severity	Alert  (click "▶" to expand/collapse)
Warn		Obfuscated code: npm @storybook/addon-onboarding is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: packages/storybook/package.json → npm/@storybook/addon-onboarding@10.5.2 ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@storybook/addon-onboarding@10.5.2. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		Obfuscated code: npm happy-dom is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: ? → npm/@storybook/addon-vitest@10.5.2 → npm/@happy-dom/global-registrator@20.0.11 → npm/happy-dom@20.10.6 ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/happy-dom@20.10.6. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		Obfuscated code: npm rimraf is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: ? → npm/google-auth-library@10.5.0 → npm/rimraf@5.0.10 ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/rimraf@5.0.10. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		Obfuscated code: npm yargs is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: ? → npm/electron-builder@26.15.2 → npm/mint@4.2.666 → npm/@astrojs/check@0.9.6 → npm/yargs@17.7.3 ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/yargs@17.7.3. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report