@prohost/cli 0.12.0 → 0.12.1

package/CHANGELOG.md

@@ -4,6 +4,13 @@ Versions follow [semver](https://semver.org/). Publishing is automated: merging
 a version bump to `main` triggers `.github/workflows/npm-publish-cli.yml`, which
 builds via `prepack`, runs the suite, publishes, and tags `cli-v<version>`.
 
+## 0.12.1
+
+- **An account the 0.10.1-row upload un-reports waits for its next report.**
+  When the server skips that account's version-1 rows as not reported, its
+  other pending days are no longer sent the same tick (which drew a
+  `not_reported` skip and a strike); they go after its next accepted report.
+
 ## 0.12.0
 
 - **`agent run` handles up to three conversations at once by default.**

package/dist/usage/service.js

@@ -259,10 +259,11 @@ export class UsageService {
         }
         // A pair whose version-1 rows are still pending (throttled, partly accepted, or waiting for a
         // report) holds its rebuilt rows back: sent now, they could be overwritten by those stale rows
-        // landing on a later tick. They stay dirty and go once the legacy rows settle.
+        // landing on a later tick. They stay dirty and go once the legacy rows settle. An account that
+        // upload un-reported (`ready` was filtered before it) waits for its next accepted report too,
+        // rather than sending its other days into a `not_reported` skip and a strike.
         const heldByLegacy = legacyUnsentPairs(scan);
-        if (heldByLegacy.size > 0)
-            ready = ready.filter((r) => !heldByLegacy.has(pendingKey(r.day, r.accountKey)));
+        ready = ready.filter((r) => this.reportedKeys.has(r.accountKey) && !heldByLegacy.has(pendingKey(r.day, r.accountKey)));
         const legacyReady = new Set(ready.map((r) => pendingKey(r.day, r.accountKey)).filter((pair) => scan.legacy[pair] !== undefined));
         if (legacyReady.size > 0) {
             if (!(await this.serverReplacesDays(api, machineId, machine))) {

package/dist/version.d.ts

@@ -7,6 +7,6 @@
  * `package.json`, so a release bump that forgets this file fails the suite
  * instead of shipping a `User-Agent` that lies about which build is calling.
  */
-export declare const CLI_VERSION = "0.12.0";
+export declare const CLI_VERSION = "0.12.1";
 /** Sent on every HTTP request the CLI makes back into ProhostAI. */
-export declare const USER_AGENT = "prohost-cli/0.12.0";
+export declare const USER_AGENT = "prohost-cli/0.12.1";

package/dist/version.js

@@ -7,6 +7,6 @@
  * `package.json`, so a release bump that forgets this file fails the suite
  * instead of shipping a `User-Agent` that lies about which build is calling.
  */
-export const CLI_VERSION = '0.12.0';
+export const CLI_VERSION = '0.12.1';
 /** Sent on every HTTP request the CLI makes back into ProhostAI. */
 export const USER_AGENT = `prohost-cli/${CLI_VERSION}`;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@prohost/cli",
-  "version": "0.12.0",
+  "version": "0.12.1",
   "description": "Run your own AI agent as a ProhostAI teammate, and stream your account's webhooks to your laptop.",
   "type": "module",
   "license": "MIT",