Which copy did ZCode's wiki upload leave in the cloud?

The fault the changelog names

ZCode 3.14.0, in release notes dated 19 September 2026, says it fixed abnormal uploads in the repository wiki. The sentence admits a product fault; it does not say whether the departing object was .git objects, an LFS cache, or filtered source text.^[1]

The same note also adds an approval dialog that can grant full access and workflows that bind multiple sub-agents from one script. Those items do not bound the upload path; they only show the product opened other doors on the same day.^[1]

The copy the independent dump measured

ferstar writes that, while a session is signed in, a workspace is encrypted and sent to Aliyun OSS before a prompt and after a Repo Wiki refresh. In one example a 345,549,173-byte workspace packed to 313,070,842 encrypted bytes; the author reads the weight as sitting on the .git side.^[2]

The post argues that the in-app experience and indexing toggles do not stop capture, and that a valid JWT keeps the pipeline up. A 19 September update table claims the remediated build dropped the full snapshot. That table is the author's own diff, not a third-party examination record.^[2]

The gap neither text closes

The changelog says an abnormal upload; the dump measures an encrypted workspace copy. They sit on the same incident chain; one names the fault in product language, the other names departing bytes on a single machine. That the object is still the same copy does not follow from either text.^{[1], [2]}

The gap holds until an examination from outside the author's machine shows which paths the remediated client deleted. Neither of today's texts carries that examination.^{[1], [2]}