统一仓库链接与依赖，迁移至 VelaShellLabs 组织

本次提交将所有涉及 joesdu 组织的链接、说明、依赖项统一替换为 VelaShellLabs，包括文档、CI/CD、NuGet 发布策略等。更新了 README、release.yml、Directory.Build.props、release-process.md、cli.md 等文件中的仓库地址和文档链接。将 VelaShell.Plugin.Cli.csproj 和 VelaShell.PluginSdk.Build.csproj 中 VelaShell.PluginSdk 依赖版本固定为 1.5.1，并移除相关变量定义。同步更新项目元数据，消除与原组织的耦合，为仓库迁移做准备。

Author: joesdu

.github/workflows/release.yml

@@ -10,7 +10,7 @@
 # 现象是插件作者构建到一半 Exec 失败 —— 所以它俩是一个发布单元,拆库时刻意留在同仓库。
 #
 # **另外三个包不在这里发**(2026-08-27 拆库起):
-#      VelaShell.PluginSdk / .Testing …… joesdu/velashell-plugin-sdk
+#      VelaShell.PluginSdk / .Testing …… VelaShellLabs/velashell-plugin-sdk
 #      VelaShell.Plugin.Templates ……… joesdu/velashell-plugin-templates
 # 三个仓库各有各的版本号。本仓库发 1.5.3 不代表契约动了,也不要求模板跟着发。
 #
@@ -36,7 +36,7 @@
 #   NuGet/login 拿本次运行的 GitHub OIDC 令牌去 nuget.org 换一把**短时效**的推送密钥,
 #   用完即弃。
 #   ⚠️ 首次发版前必须在 nuget.org 上为**本仓库**建一条可信发布策略:
-#        Repository owner  joesdu
+#        Repository owner  VelaShellLabs
 #        Repository        velashell-plugin-cli
 #        Workflow file     release.yml
 #      建法见 docs/release-process.md 的「NuGet 可信发布」一节。

Directory.Build.props

@@ -23,7 +23,7 @@
       targets 没跟上,现象是插件作者构建到一半 Exec 失败 —— 所以它俩是一个发布单元。
 
       **与契约 SDK 解耦**(2026-08-27 拆库起):VelaShell.PluginSdk 在
-      joesdu/velashell-plugin-sdk,有自己的版本号。SDK 发 1.6.0 不要求本仓库跟着发;
+      VelaShellLabs/velashell-plugin-sdk,有自己的版本号。SDK 发 1.6.0 不要求本仓库跟着发;
       本仓库发 1.5.3 也不代表契约动了。想吃到新契约时,把下面的
       VelaSdkDependencyVersion 抬上来再发一版即可。
 
@@ -41,24 +41,6 @@
     <IncludeSourceRevisionInInformationalVersion>false</IncludeSourceRevisionInInformationalVersion>
   </PropertyGroup>
 
-  <PropertyGroup>
-    <!--
-      本仓库引用的**契约 SDK 包版本**。这是拆库之后唯一的跨仓库依赖旋钮:
-
-        · vela-plugin 用 SDK 里的 VpxContainer / PluginManifestReader —— 宿主装包与工具
-          出包必须走同一份实现,否则"本机打得出、宿主装不上"这种事迟早发生;
-        · VelaShell.PluginSdk.Build 把它以 PrivateAssets="none" 传给插件工程,
-          于是插件作者引一个 .Build 就拿到了契约程序集。
-
-      **抬这个版本 = 让插件作者的编译目标契约变新**。抬完记得:
-        ① 核对 VelaAvaloniaVersion 与新 SDK 导出的 $(VelaSdkPinnedAvaloniaVersion) 一致
-           (下面 VerifyAvaloniaVersionPin 会在构建期比一遍,不用担心漏);
-        ② 发一版本仓库的包,插件作者才吃得到。
-      不抬也完全正常 —— 老契约照样能打包、能校验。
-    -->
-    <VelaSdkDependencyVersion Condition="'$(VelaSdkDependencyVersion)' == ''">1.5.0</VelaSdkDependencyVersion>
-  </PropertyGroup>
-
   <PropertyGroup>
     <!--
       插件与宿主必须用同一版本的 Avalonia:装载器强制让 Avalonia* 回落到宿主那一套
@@ -81,9 +63,9 @@
   	<Authors>joesdu</Authors>
   	<PackagePrefix>VelaShell</PackagePrefix>
   	<RepositoryType>git</RepositoryType>
-  	<RepositoryUrl>https://github.com/joesdu/velashell-plugin-cli</RepositoryUrl>
+  	<RepositoryUrl>https://github.com/VelaShellLabs/velashell-plugin-cli</RepositoryUrl>
   	<PackageLicenseExpression>AGPL-3.0-only</PackageLicenseExpression>
-  	<PackageProjectUrl>https://github.com/joesdu/velashell-plugin-cli</PackageProjectUrl>
+  	<PackageProjectUrl>https://github.com/VelaShellLabs/velashell-plugin-cli</PackageProjectUrl>
   	<GenerateAssemblyConfigurationAttribute>True</GenerateAssemblyConfigurationAttribute>
   	<GenerateAssemblyCompanyAttribute>True</GenerateAssemblyCompanyAttribute>
   	<GenerateAssemblyProductAttribute>True</GenerateAssemblyProductAttribute>

README.md

@@ -23,7 +23,7 @@ vela-plugin update                          # 以后升级
 兼容性;`--source` 可以指到自建商店。完整命令见 [`docs/cli.md`](docs/cli.md)。
 
 写自己的插件:见
-[开发指南](https://github.com/joesdu/velashell-plugin-templates/blob/main/docs/dev-guide.md)。
+[开发指南](https://github.com/VelaShellLabs/velashell-plugin-templates/blob/main/docs/dev-guide.md)。
 
 ## 为什么这两个包在同一个仓库
 
@@ -40,9 +40,9 @@ sdk 仓库要去引用 CLI 包,于是 SDK 发版被 CLI 卡住 —— 正是拆
 
 | 仓库 | 产出 | 什么时候发 |
 | --- | --- | --- |
-| [`velashell-plugin-sdk`](https://github.com/joesdu/velashell-plugin-sdk) | `VelaShell.PluginSdk`、`.Testing` | 契约有增删改时 |
+| [`velashell-plugin-sdk`](https://github.com/VelaShellLabs/velashell-plugin-sdk) | `VelaShell.PluginSdk`、`.Testing` | 契约有增删改时 |
 | **本仓库** `velashell-plugin-cli` | `VelaShell.Plugin.Cli`、`VelaShell.PluginSdk.Build` | 工具/打包/MSBuild 逻辑变化时 |
-| [`velashell-plugin-templates`](https://github.com/joesdu/velashell-plugin-templates) | `VelaShell.Plugin.Templates` | 模板内容变化,或要把新建工程指到新版 Build 包时 |
+| [`velashell-plugin-templates`](https://github.com/VelaShellLabs/velashell-plugin-templates) | `VelaShell.Plugin.Templates` | 模板内容变化,或要把新建工程指到新版 Build 包时 |
 
 依赖方向是单向的,没有环:
 
@@ -55,7 +55,7 @@ velashell-plugin-templates
 ```
 
 另外两个相关仓库:[joesdu/VelaShell](https://github.com/joesdu/VelaShell)(宿主主程序)、
-[joesdu/velashell-plugins](https://github.com/joesdu/velashell-plugins)(第一方插件)。
+[joesdu/velashell-plugins](https://github.com/VelaShellLabs/velashell-plugins)(第一方插件)。
 
 ## 两个跨仓库旋钮
 

docs-en/README.md

@@ -13,9 +13,9 @@ After the 2026-08-27 split, each document lives next to the package it describes
 
 | Document | Where it lives now |
 | --- | --- |
-| **Development guide** (tutorial: writing your first plugin) | [velashell-plugin-templates / docs-en/dev-guide.md](https://github.com/joesdu/velashell-plugin-templates/blob/main/docs-en/dev-guide.md) |
-| **Packaging and publishing** | [velashell-plugin-templates / docs-en/publishing.md](https://github.com/joesdu/velashell-plugin-templates/blob/main/docs-en/publishing.md) |
-| **SDK reference** | [velashell-plugin-sdk / docs-en/sdk-reference.md](https://github.com/joesdu/velashell-plugin-sdk/blob/main/docs-en/sdk-reference.md) |
+| **Development guide** (tutorial: writing your first plugin) | [velashell-plugin-templates / docs-en/dev-guide.md](https://github.com/VelaShellLabs/velashell-plugin-templates/blob/main/docs-en/dev-guide.md) |
+| **Packaging and publishing** | [velashell-plugin-templates / docs-en/publishing.md](https://github.com/VelaShellLabs/velashell-plugin-templates/blob/main/docs-en/publishing.md) |
+| **SDK reference** | [velashell-plugin-sdk / docs-en/sdk-reference.md](https://github.com/VelaShellLabs/velashell-plugin-sdk/blob/main/docs-en/sdk-reference.md) |
 
 Each carries the **version banner of its own package**, which is why it has to live next to that
 package: keeping them here would mean every SDK release needs a commit in this repository — the

docs-en/cli.md

@@ -1,7 +1,7 @@
 # `vela-plugin` CLI Manual
 
 > Applies to vela-plugin **1.5.0** (`vela-plugin --version` tells you what you have).
-> See also (other repositories): [Development Guide](https://github.com/joesdu/velashell-plugin-templates/blob/main/docs-en/dev-guide.md) · [Packaging and Publishing](https://github.com/joesdu/velashell-plugin-templates/blob/main/docs-en/publishing.md) · [SDK Reference](https://github.com/joesdu/velashell-plugin-sdk/blob/main/docs-en/sdk-reference.md)
+> See also (other repositories): [Development Guide](https://github.com/joesdu/velashell-plugin-templates/blob/main/docs-en/dev-guide.md) · [Packaging and Publishing](https://github.com/joesdu/velashell-plugin-templates/blob/main/docs-en/publishing.md) · [SDK Reference](https://github.com/VelaShellLabs/velashell-plugin-sdk/blob/main/docs-en/sdk-reference.md)
 
 `vela-plugin` is the plugin author's command-line tool. It calls the same implementation the
 host uses (`VelaShell.PluginSdk`: manifest parsing, `.vpx` container, signature verification),

docs/README.md

@@ -13,9 +13,9 @@
 
 | 文档 | 去了哪 |
 | --- | --- |
-| **开发指南**(教程式,写第一个插件) | [velashell-plugin-templates / docs/dev-guide.md](https://github.com/joesdu/velashell-plugin-templates/blob/main/docs/dev-guide.md) |
-| **打包与发布**(`.vpx`、签名、发到插件商店) | [velashell-plugin-templates / docs/publishing.md](https://github.com/joesdu/velashell-plugin-templates/blob/main/docs/publishing.md) |
-| **SDK 参考**(契约表面、能力域一览) | [velashell-plugin-sdk / docs/sdk-reference.md](https://github.com/joesdu/velashell-plugin-sdk/blob/main/docs/sdk-reference.md) |
+| **开发指南**(教程式,写第一个插件) | [velashell-plugin-templates / docs/dev-guide.md](https://github.com/VelaShellLabs/velashell-plugin-templates/blob/main/docs/dev-guide.md) |
+| **打包与发布**(`.vpx`、签名、发到插件商店) | [velashell-plugin-templates / docs/publishing.md](https://github.com/VelaShellLabs/velashell-plugin-templates/blob/main/docs/publishing.md) |
+| **SDK 参考**(契约表面、能力域一览) | [velashell-plugin-sdk / docs/sdk-reference.md](https://github.com/VelaShellLabs/velashell-plugin-sdk/blob/main/docs/sdk-reference.md) |
 
 它们各自带着**自己那个包的版本号横幅**,所以必须跟包同仓库 —— 留在这里的话,
 契约 SDK 发一版就要来改本仓库的文档,正是拆库要消掉的那种牵连。

docs/cli.md

@@ -1,7 +1,7 @@
 # `vela-plugin` 命令行手册
 
 > 适用版本:vela-plugin **1.5.0**(`vela-plugin --version` 看本机装的是哪版)。
-> 相关文档(在别的仓库):[开发指南](https://github.com/joesdu/velashell-plugin-templates/blob/main/docs/dev-guide.md) · [打包与发布](https://github.com/joesdu/velashell-plugin-templates/blob/main/docs/publishing.md) · [SDK 参考](https://github.com/joesdu/velashell-plugin-sdk/blob/main/docs/sdk-reference.md)
+> 相关文档(在别的仓库):[开发指南](https://github.com/joesdu/velashell-plugin-templates/blob/main/docs/dev-guide.md) · [打包与发布](https://github.com/joesdu/velashell-plugin-templates/blob/main/docs/publishing.md) · [SDK 参考](https://github.com/VelaShellLabs/velashell-plugin-sdk/blob/main/docs/sdk-reference.md)
 
 `vela-plugin` 是插件作者的命令行工具。它与宿主共用同一份实现(`VelaShell.PluginSdk`
 里的清单解析、`.vpx` 容器读写、签名校验),所以**不存在"工具认、宿主不认"的缝**。

docs/release-process.md

@@ -1,7 +1,7 @@
 # 发版流程(CLI + 构建支持包)
 
 > 本篇只讲**本仓库**怎么发版。契约 SDK 见
-> [velashell-plugin-sdk](https://github.com/joesdu/velashell-plugin-sdk/blob/main/docs/release-process.md),
+> [velashell-plugin-sdk](https://github.com/VelaShellLabs/velashell-plugin-sdk/blob/main/docs/release-process.md),
 > `dotnet new` 模板见
 > [velashell-plugin-templates](https://github.com/joesdu/velashell-plugin-templates/blob/main/docs/release-process.md)。
 
@@ -63,7 +63,7 @@ Actions 页面 → 选 Release 工作流 → Run workflow → 填标签。推送
 | --- | --- |
 | Policy name | `velashell-plugin-cli`(随意,能认出来就行) |
 | Policy owner | `joes_du` |
-| Repository Owner | `joesdu` |
+| Repository Owner | `VelaShellLabs` |
 | **Repository** | `velashell-plugin-cli` |
 | **Workflow File** | `release.yml` —— **只填文件名**,不要写 `.github/workflows/` 前缀 |
 | Environment | 留空(工作流没用 GitHub Environments) |

src/VelaShell.Plugin.Cli/README.md

@@ -67,7 +67,7 @@ vela-plugin dev init      # 生成 IDE 启动配置(读 ~/.velashell/host.json 
 插件工程 `dotnet build -t:PackVpx` 直接出包。装全局工具是为了开发内环、体检、
 签名与包检查。
 
-- 命令行手册:<https://github.com/joesdu/velashell-plugin-cli/blob/main/docs/cli.md>
-- 插件开发指南:<https://github.com/joesdu/velashell-plugin-templates/blob/main/docs/dev-guide.md>
-- 打包与发布:<https://github.com/joesdu/velashell-plugin-templates/blob/main/docs/publishing.md>
+- 命令行手册:<https://github.com/VelaShellLabs/velashell-plugin-cli/blob/main/docs/cli.md>
+- 插件开发指南:<https://github.com/VelaShellLabs/velashell-plugin-templates/blob/main/docs/dev-guide.md>
+- 打包与发布:<https://github.com/VelaShellLabs/velashell-plugin-templates/blob/main/docs/publishing.md>
 - 插件商店:<http://market.easilynet.top>

src/VelaShell.Plugin.Cli/VelaShell.Plugin.Cli.csproj

@@ -19,19 +19,7 @@
   </PropertyGroup>
 
   <ItemGroup>
-    <!--
-      容器读写与清单校验都在契约 SDK 里:宿主装包与工具出包必须走同一份实现,
-      否则「本机打得出、宿主装不上」这种事迟早发生。
-
-      拆库(2026-08-27)之后这里从 ProjectReference 变成 PackageReference ——
-      SDK 在 joesdu/velashell-plugin-sdk,按 NuGet 取。版本旋钮
-      VelaSdkDependencyVersion 在仓库根 Directory.Build.props,抬它才吃到新契约。
-
-      注:SDK 的 dll 会随之复制进本工程的输出目录,这是**需要的** ——
-      VelaShell.PluginSdk.Build 把整个输出目录收进包的 tools/net11.0/,
-      `dotnet exec VelaShell.Plugin.Cli.dll` 在插件作者机器上要靠它才跑得起来。
-    -->
-    <PackageReference Include="VelaShell.PluginSdk" Version="$(VelaSdkDependencyVersion)" />
+    <PackageReference Include="VelaShell.PluginSdk" Version="1.5.1" />
   </ItemGroup>
 
   <ItemGroup>