@data-matters.io/agent-harness 0.1.9 → 0.1.10

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@data-matters.io/agent-harness",
-  "version": "0.1.9",
+  "version": "0.1.10",
   "description": "Spec-Driven Development with Claude Code: gates, task loop and standards installed into a product repository",
   "license": "UNLICENSED",
   "repository": {

package/templates/.harness/lib.sh

@@ -47,6 +47,15 @@ harness_session_error_text() {
       : raw);' "$1" 2>/dev/null
 }
 
+# harness_session_api_error <session.json>: the session's api_error field, the
+# structured value the runtime sets when the API refused (usage_limit_reached).
+# Empty when the session carries none.
+harness_session_api_error() {
+  node -e "$harness_session_js"'
+    const d = session(process.argv[1]);
+    process.stdout.write(typeof d.api_error === "string" ? d.api_error : "");' "$1" 2>/dev/null
+}
+
 # harness_api_refused <session.json>: the session ended on an error that says
 # the API cannot serve it: no credit, a quota, a spend or usage limit, billing,
 # an invalid key, or the gateway itself failing (503 or another 5xx, a
@@ -156,8 +165,30 @@ harness_claude_flags() {
 # session limit") and sets api_error to usage_limit_reached, so both are matched;
 # the gateway's Portuguese quota message is matched too, and its transient 429
 # is not (quota.sh, ADR 0025 section 8).
+#
+# Only the session's own FAILURE is read: the api_error field, and the error
+# text of a session that ended with is_error (harness_session_error_text).
+# The answer of a session that ended well is never a usage error by what it
+# says: a task that explains an old quota event ("cota semanal") is a task
+# about a quota, not a quota. The one exception is the gateway's quota notice,
+# which arrives unmarked, in the body of a 200: there the whole answer IS the
+# notice, so a short answer that carries a quota marker still is a usage error
+# (harness_quota_notice_unmarked).
 harness_usage_error() {
-  harness_quota_exhausted "$(cat -- "$1" 2>/dev/null)"
+  local text reply
+  text="$(harness_session_error_text "$1")"
+  if [[ -n "$text" ]]; then
+    # The session failed: its error text (its result and its api_error) is the
+    # message the rule is about.
+    if harness_quota_exhausted "$text"; then return 0; fi
+    return 1
+  fi
+  # The session ended well: its answer is not a usage error by what it says.
+  # The api_error field still counts (usage_limit_reached), and the gateway's
+  # unmarked notice is the one answer that IS the notice.
+  if harness_quota_exhausted "$(harness_session_api_error "$1")"; then return 0; fi
+  reply="$(harness_session_reply "$1")" || return 1
+  harness_quota_notice_unmarked "$reply"
 }
 
 # harness_level_descend <level>: the level one below, for the fallback after a

package/templates/.harness/quota.sh

@@ -11,6 +11,10 @@
 #       a quota marker and no transient marker. A 429 alone is not enough in
 #       either direction: both gateway messages carry the same structured
 #       fields, so only the text tells them apart.
+#   (c) is a session that ENDED WELL the gateway's quota notice?
+#       harness_quota_notice_unmarked <text>
+#       the gateway sometimes answers 200 with the quota notice in the body,
+#       without marking it as an error: there the whole answer is the notice.
 # A transient 429 (harness_quota_transient) is neither: it may be retried and
 # changes nothing.
 #
@@ -52,6 +56,25 @@ harness_quota_exhausted() {
   grep -qE -- "$harness_quota_markers" <<<"$t" && ! grep -qE -- "$harness_quota_transient_markers" <<<"$t"
 }
 
+# The longest text that can be the gateway's quota notice. The notice arrives
+# in the body of a 200 response, without being marked as an error (the rule of
+# the watchdog, vps-bootstrap, 2026-11-11): there the whole answer IS the
+# notice. A long answer that talks about a quota is a task about a quota, not a
+# quota.
+harness_quota_notice_max_len=400
+
+# harness_quota_notice_unmarked <text>: the text is the gateway's quota notice
+# that arrived unmarked: a SHORT message (at most harness_quota_notice_max_len
+# characters) that carries a quota marker. The markers are the ones above (one
+# list, ADR 0025 section 8): this rule only says how much of the answer may
+# be the notice.
+harness_quota_notice_unmarked() {
+  local t="$1" len
+  len=${#t}
+  (( len <= harness_quota_notice_max_len )) || return 1
+  harness_quota_exhausted "$t"
+}
+
 # harness_api_unreachable <text>: the gateway failed (503 or another 5xx, a
 # connection failure, a timeout): the API does not answer, whatever the quota.
 harness_api_unreachable() {