@integrity-labs/agt-cli 0.28.668 → 0.28.670

package/dist/{chunk-4GA4K2BF.js → chunk-HGVJVYKW.js}

@@ -297,7 +297,7 @@ is the failure this rule exists to stop.
 var ACTIVE_TASKS_MAX_CHARS = 800;
 var ACTIVE_TASKS_TRUNCATION_SUFFIX = "\u2026 (truncated)\n\n";
 function sanitizePromptText(value) {
-  return value.replace(/[-]+/g, " ").replace(/\s+/g, " ").trim();
+  return value.replace(/[\u0000-\u001F\u007F]+/g, " ").replace(/\s+/g, " ").trim();
 }
 function buildActiveTasksSection(activeTasks) {
   if (!activeTasks || activeTasks.length === 0)
@@ -4982,29 +4982,40 @@ var FLAG_REGISTRY = [
     // write path, not a host's local environment file. One more reason not to
     // canary with it.
     envVar: "AGT_MEMORY_TOMBSTONES_ENABLED",
-    // Deliberately unreachable placeholder: the reader is not published yet.
+    // Pinned to the first PUBLISHED agt-cli whose manager carries a WORKING
+    // reader, verified against the tarball rather than inferred from the merge.
+    // ENG-9229 + ENG-9257 merged as 91a67cb08, but auto-publish patch-bumps
+    // from whatever is on main, so the merge does not name a version: a second
+    // CLI-touching merge landed eight minutes later, and `latest` was already
+    // past our cut by the time anyone looked. What settles it is
+    // `npm pack @integrity-labs/agt-cli@<v>` + grep of
+    // package/dist/lib/manager-worker.js (the manager is the actual reader; the
+    // dist/mcp/* occurrences are bundling artifacts). 0.28.666 carries NONE of
+    // `_memory-retirement`, `memory-file-tombstones`, `applyMemoryTombstones`,
+    // `memory-retirement-report`; 0.28.667 carries all four.
     //
-    // It must be PARSEABLE and unreachable, not omitted and not garbage.
-    // classifyHostReach (packages/core/src/feature-flags/reach.ts) maps an
-    // empty `since` to `honors` for EVERY host including ones with no reader at
-    // all, and maps an unparseable one to `unknown` — which collides with the
-    // "host reports no agt_version" class, so an operator cannot tell "not
-    // shipped yet" from "these hosts are unreadable". '99.99.99' classifies
-    // every host `stale`, which is the honest pre-publication answer.
+    // ALL FOUR, because this has to name the first build where flipping the
+    // flag does what the flag SAYS, not merely the first build with a reader:
+    // the write-time manifest gate, the tombstone pass sitting above the
+    // download short-circuit, the response hash covering the tombstone list,
+    // and the report-back. Ship a build missing any of those and reach reports
+    // `honors` for hosts that silently never act. Here they shipped in one
+    // merge so they could not be split across versions - that is a property of
+    // this cut, not a guarantee about the next one.
     //
-    // Note '0.29.0' is used elsewhere for the same purpose but is weaker: it is
-    // unreachable only by accident of auto-publish patch-bumping 0.28.x, so one
-    // deliberate minor bump would silently reclassify the whole fleet `honors`.
+    // MOVE THIS PIN whenever a change alters what arming the flag DOES on a
+    // host, to the first version carrying the CHANGED behaviour, and verify
+    // that one against the tarball too (apps/cli/package.json is not the
+    // published number). See `tool-call-audit` above, where the pin was NOT
+    // moved at such a merge and went stale for a day.
     //
-    // REPLACE IT AT THE **CLI** MERGE, not the API merge — `since` describes
-    // what the HOST can act on — with the published tarball's version (verify
-    // via `npm pack`; apps/cli/package.json is not the published number). And
-    // it must name the first build where flipping the flag does what this flag
-    // SAYS, not merely the first build with a reader: that means the manifest
-    // gate, the tombstone pass sitting above the download short-circuit, and
-    // the response hash covering the tombstone list. Ship a build missing any
-    // of those and reach reports `honors` for hosts that silently never act.
-    since: "99.99.99"
+    // WHY THIS FIELD IS NEVER OMITTED, whatever it is set to. classifyHostReach
+    // (packages/core/src/feature-flags/reach.ts) maps an empty `since` to
+    // `honors` for EVERY host including ones with no reader at all, and maps an
+    // unparseable one to `unknown` - which collides with the "host reports no
+    // agt_version" class, so an operator cannot tell "not shipped yet" from
+    // "these hosts are unreadable". Both outlive this particular version.
+    since: "0.28.667"
   },
   {
     key: "conversation-eval-backend",
@@ -12421,4 +12432,4 @@ export {
   minutesSinceLocalMidnight,
   peekCurrentSession
 };
-//# sourceMappingURL=chunk-4GA4K2BF.js.map
+//# sourceMappingURL=chunk-HGVJVYKW.js.map