Preparing a folder for a cloud session now packages it and hands it off without uploading.
tengu_ccr_bundle_seed_enabled Gate removed from the codeThis release deleted the gate from the code while it was still reading on for the account this site reads, so the code path no longer asks a flag before running.
This account: on · anonymous baseline: on · compiled default in v2.1.248: not a boolean we can read
Read once, for one account on one subscription tier, against v2.1.248. It isn't a statement about your account. What a flag value here can and cannot tell you
What's wrong with this entry?
Preparing a folder to seed a cloud session now packages it and stops, reporting an outcome of "built" and handing the packaged seed back to its caller, where it previously also uploaded the bundle and reported it as shipped. The upload of the same bundle still exists on a separate path-based route, so this looks like the upload moving rather than going away.
- The routine now receives its size ceiling and storage version as parameters instead of working them out itself.
- Upstream gating is unchanged: the
CCR_ENABLE_BUNDLEenvironment variable or thetengu_ccr_bundle_seed_enabledflag. - Where the built folder seed is uploaded afterwards is not settled by the seeding code itself.
outcome: S("built")
Strings lifted out of the shipped bundle, so the claim above can be checked against them.