crewly 1.20.355 → 1.20.356

package/dist/backend/backend/src/constants.js

@@ -1523,6 +1523,19 @@ export const EVENT_BUS_CONSTANTS = {
      *  replayed publish of the same event is not delivered twice (#926) */
     DELIVERED_EVENT_TTL_MS: 30 * 60 * 1000,
 };
+/**
+ * Recurring "TL progress check" scheduled by the team-leader delegate-task
+ * skill. Off by default (the lead is woken by the worker's agent:idle event
+ * and by report-status); an opted-in check never fires more often than
+ * MIN_INTERVAL_MINUTES. The 5-minute default woke Claude sessions 219 times
+ * in 3.5 days (2026-10-16).
+ */
+export const DELEGATION_PROGRESS_CHECK_CONSTANTS = {
+    /** Message prefix the skill uses; identifies these checks in the scheduler */
+    MESSAGE_PREFIX: 'TL progress check:',
+    /** Shortest allowed interval (minutes) for a recurring delegation progress check */
+    MIN_INTERVAL_MINUTES: 30,
+};
 /**
  * Constants for Slack thread file storage.
  * Used by SlackThreadStoreService to persist thread conversations
@@ -4032,6 +4045,8 @@ export const AGENT_MESSAGE_DELIVERY_CONSTANTS = {
 export const SUB_AGENT_QUEUE_CONSTANTS = {
     /** Wait this long after an agent goes down before waking it for its queued messages (ms) */
     QUEUED_WAKE_DELAY_MS: 5_000,
+    /** After boot, pause before starting agents that were down with messages queued (lets the restore queue claim its own first; a start in between drains the queue and ends the retry) */
+    BOOT_QUEUED_WAKE_DELAY_MS: 60_000,
     /** At most one such wake per agent in this window, so a crashing agent is not relaunched in a loop (ms) */
     QUEUED_WAKE_COOLDOWN_MS: 10 * 60 * 1000,
     /** Maximum messages per agent before dropping oldest */
@@ -6907,6 +6922,10 @@ export const OPEN_ITEMS_CONSTANTS = {
     ASK_OWNER_DEDUPE_WINDOW_MS: 2 * 60 * 60 * 1000,
     /** Two questions with at least this character-bigram overlap are the same question */
     SAME_QUESTION_SIMILARITY: 0.5,
+    /** Window (ms) for counting an agent's lifted-question cards (#1334) */
+    REPLY_CARD_WINDOW_MS: 24 * 60 * 60 * 1000,
+    /** At most this many lifted-question cards per agent per window; later questions are tracked without a card (#1334) */
+    REPLY_CARDS_PER_AGENT_PER_DAY: 3,
     /** Option labels of a derived card */
     YES_LABEL: 'Yes',
     NO_LABEL: 'No',
@@ -7373,6 +7392,14 @@ export const RUNTIME_FALLBACK_CONSTANTS = {
     TRANSIENT_ESCALATED_HORIZON_MS: 30 * 60_000,
     /** A revert is not attempted while the PTY wrote within this window */
     IDLE_QUIET_MS: 20_000,
+    /**
+     * A session's model turn (a Claude Code PreToolUse hook) counts as proof that
+     * its runtime target has usage only this long after the target was marked out
+     * of usage (a response already streaming when the limit hit is not proof)
+     */
+    WORKING_EVIDENCE_GRACE_MS: 2 * 60_000,
+    /** Working-evidence reports of one session are looked at no more often than this */
+    WORKING_EVIDENCE_THROTTLE_MS: 60_000,
     /** Smoke tests */
     SMOKE: {
         TEAM_PREFIX: 'zz-runtime-smoke-',
@@ -7406,6 +7433,44 @@ export const RUNTIME_FALLBACK_CONSTANTS = {
         'crewly-agent': 'Crewly Agent',
     },
 };
+/**
+ * Per-session usage-limit state (2026-10-16 incident: the orchestrator sat on
+ * Claude Code's weekly-limit menu for ~38 hours while Crewly restarted it,
+ * waited for its prompt, and reported it "active and ready"). While a session
+ * is usage-limited it is not restarted, not waited on and not written to.
+ */
+export const USAGE_LIMIT_STATE_CONSTANTS = {
+    /** How long to back off when the limit message names no reset time (ms) */
+    NO_RESET_BACKOFF_MS: 30 * 60 * 1000,
+    /** Grace after the parsed reset time before the session is tried again (ms) */
+    RESET_GRACE_MS: 2 * 60 * 1000,
+    /**
+     * Furthest a parsed reset time may lie ahead. Weekly limits reset within
+     * 7 days; a dated message further out is an old one (a past "Oct 10" is
+     * read as next year's), so it is not trusted.
+     */
+    MAX_RESET_AHEAD_MS: 8 * 24 * 60 * 60 * 1000,
+    /** Trailing non-empty screen lines inspected for a usage-limit state */
+    SCREEN_TAIL_LINES: 25,
+    /** Longest a held queue waits before looking at the state again (ms) */
+    RECHECK_MAX_MS: 60_000,
+    /** Delay between the keys that answer the usage-limit menu (ms) */
+    MENU_KEY_DELAY_MS: 300,
+    /** Marker on a delivery result held because the agent is usage-limited */
+    QUEUED_MARKER: '[USAGE_LIMITED]',
+    /**
+     * Fewest printable characters (whitespace collapsed) a live output chunk
+     * needs to count as fresh activity that lifts a usage-limit state; cursor
+     * moves and spinner ticks stay below it.
+     */
+    FRESH_OUTPUT_MIN_CHARS: 40,
+    /**
+     * After a limit is last seen (or its menu answered), activity this soon is
+     * not trusted to lift the state: it is the repaint of the limit screen or
+     * of the key Crewly pressed (ms).
+     */
+    LIFT_GRACE_MS: 10_000,
+};
 /**
  * Per-person access (issue #968, epic #967): the people directory, the person
  * each agent turn acts for, and grant sharing. specs/per-person-access.md