ChainVeinFabric

自动挖掘不再是独立模式：在任意挖掘模式中按住 Ctrl 点击主开关即可待命，每次左键只触发一轮以玩家为中心的搜索与挖掘；点击 AUTO 可直接解除

新增自动挖掘冷却与高可见度危险提示 HUD；同类相邻算法以玩家脚下方块为目标，其余白名单与形状算法继续复用统一异步搜索路径

新增持久化的权限等级 4 命令：/chainvein maxBlocks [1..2048]（默认 256）与 /chainvein pickupRadius [0..64]（默认 10）

服务端挖掘请求不再使用硬编码玩家距离，也不会为请求加载区块；连锁交互交由原版服务端交互距离判断

快捷潜影盒优先使用新的标准 Fabric Storage API：先解析随身存储槽位，再对整批溢出物全局合并已有堆叠并使用空槽；装不下的剩余物仍正常掉落。旧公开 API 继续作为能力探测后的回退路径

Minecraft 26.2 的可选 Litematica 最低兼容版本放宽至 0.28.3

纯客户端回退不再于同一 tick 发送开始与结束挖掘包；现在逐方块遵循原版挖掘进度、工具速度与方块间延迟

纯客户端挖掘会在状态 HUD 显示当前方块进度与请求进度，服务端批量挖掘路径不受影响

多次提交纯客户端挖掘请求时，会先完成当前已经开始的方块，再丢弃旧请求尚未开始的部分并切换到最新请求

稳定了纯客户端掉落测试场地，避免掉落实体滚出测试范围造成偶发误报

Automatic mining is no longer a separate mode. Ctrl-click the main toggle in any mining mode to arm it; each left click triggers exactly one player-centered search-and-mine batch, and clicking AUTO disarms it directly

Added an automatic-mining cooldown and a high-visibility hazard HUD. Same-type adjacency targets the block beneath the player, while the other whitelist and shape algorithms continue to use the shared asynchronous search path

Added persistent permission-level-4 commands: /chainvein maxBlocks [1..2048] (default 256) and /chainvein pickupRadius [0..64] (default 10)

Server mining requests no longer use a hard-coded player-distance limit and never load chunks for a request; chain interactions defer to the vanilla server interaction-range check

Quick Shulker now prefers its standard Fabric Storage API: carried storage slots are resolved once, then the complete overflow set is merged globally into existing stacks before empty slots are used. Remainders that do not fit still drop normally, and the legacy public API remains a capability-selected fallback

The minimum optional Litematica version for Minecraft 26.2 is now 0.28.3

Client-only fallback no longer sends start and stop mining packets in the same tick. Blocks are now mined one at a time using vanilla progress, tool speed, and the vanilla delay between blocks

Client-only mining now shows both current-block progress and request progress in the status HUD; the dedicated-server batch path is unchanged

When multiple client-only mining requests arrive, the currently started block finishes first, then the unstarted remainder of the old request is discarded in favor of the latest request

Stabilized the client-only drop fixture so item entities cannot roll outside the assertion area and cause intermittent false failures