@coderook/cli 0.19.0 → 0.20.0

package/.claude-plugin/plugin.json

@@ -2,7 +2,7 @@
   "name": "coderook",
   "displayName": "CodeRook",
   "description": "Save, browse and restore whole-snapshot versions of a project on CodeRook, from Claude Code.",
-  "version": "0.19.0",
+  "version": "0.20.0",
   "author": {
     "name": "ACCA Gaming Productions",
     "url": "https://coderook.com"

package/dist/desktop-app/src/main/staging.js

@@ -37,7 +37,38 @@ exports.describePlan = describePlan;
  * session. Naming them here means the plan can be inspected before a byte
  * moves.
  */
-exports.PACKABLE_LIMIT = 64 * 1024;
+/*
+  Below this a file travels with others in one request rather than alone.
+
+  Measured rather than guessed, twice. The first number was sixty-four
+  kilobytes, taken from a source folder where ninety-six percent of files were
+  under it. A four and a half gigabyte game then showed the opposite shape:
+  eight hundred files of three hundred kilobytes per section, each just above
+  that line and so each paying its own round trip.
+
+  What the game measured is the reason for the number. Every request costs
+  about six hundred and thirty milliseconds before any bytes move, and the
+  lane carries roughly 0.79 MB/s. So a three hundred kilobyte file spends
+  sixty percent of its time on overhead and a seven megabyte file spends
+  seven. The line belongs where the overhead stops dominating, which is a few
+  megabytes and not a few kilobytes.
+
+  Four megabytes was the first attempt and it overshot. Measured on the same
+  game twice: four hundred kilobyte files went from 1.80 to 3.24 MB/s when
+  batched, while 1.3 megabyte files went from 4.43 down to 3.88 — because
+  three concurrent batches move less than six concurrent requests once a file
+  is large enough that transfer, not overhead, dominates. The crossover is
+  around a megabyte.
+
+  It lives here, and the uploader imports it, because for a while it did not:
+  the uploader had measured its way to a megabyte while this file still said
+  sixty-four kilobytes, and sections were therefore planned by one definition
+  of "small" and then sent by another. Nothing broke, which is why it lasted —
+  the planner simply grouped files it called ordinary and the uploader batched
+  them anyway, and a second filter downstream existed to paper over the
+  disagreement.
+*/
+exports.PACKABLE_LIMIT = 1024 * 1024;
 exports.CHUNK_THRESHOLD = 16 * 1024 * 1024;
 exports.DIRECT_LIMIT = 95 * 1024 * 1024;
 function bandOf(size) {

package/dist/desktop-app/src/main/upload.js

@@ -42,29 +42,12 @@ const CHUNK_THRESHOLD = 16 * 1024 * 1024;
 */
 const UPLOAD_LANES = 6;
 /*
-  Below this a file travels with others in one request rather than alone.
-
-  Measured rather than guessed, twice. The first number came from a source
-  folder where ninety-six percent of files were under sixty-four kilobytes.
-  A four and a half gigabyte game then showed the opposite shape: eight
-  hundred files of three hundred kilobytes per section, each just above that
-  line and so each paying its own round trip.
-
-  What the game measured is the reason for the number. Every request costs
-  about six hundred and thirty milliseconds before any bytes move, and the
-  lane carries roughly 0.79 MB/s. So a three hundred kilobyte file spends
-  sixty percent of its time on overhead and a seven megabyte file spends
-  seven. The line belongs where the overhead stops dominating, which is a few
-  megabytes and not a few kilobytes.
-
-  Four megabytes was the first attempt and it overshot. Measured on the same
-  game twice: four hundred kilobyte files went from 1.80 to 3.24 MB/s when
-  batched, while 1.3 megabyte files went from 4.43 down to 3.88 — because
-  three concurrent batches move less than six concurrent requests once a file
-  is large enough that transfer, not overhead, dominates. The crossover is
-  around a megabyte.
+  What counts as small enough to travel with others, defined once in
+  staging.ts and imported here. The planner groups sections by the same line
+  the sender batches on, which for a while they did not — see the note beside
+  PACKABLE_LIMIT for what that cost.
 */
-const BATCH_FILE_LIMIT = 1024 * 1024;
+const BATCH_FILE_LIMIT = staging_js_1.PACKABLE_LIMIT;
 /** How much one batch may carry, and how many objects it may name. */
 const BATCH_BYTES = 24 * 1024 * 1024;
 const BATCH_COUNT = 256;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@coderook/cli",
-  "version": "0.19.0",
+  "version": "0.20.0",
   "description": "CodeRook from the command line, on any operating system",
   "license": "SEE LICENSE IN LICENSE.txt",
   "homepage": "https://coderook.com",