crewly 1.20.153 → 1.20.155

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

@@ -3,9 +3,11 @@
  * Re-exported from the main config constants for backend use
  */
 // Import from config directory for cross-domain constants
-import { CREWLY_CONSTANTS as CONFIG_CREWLY_CONSTANTS, AGENT_IDENTITY_CONSTANTS as CONFIG_AGENT_IDENTITY_CONSTANTS, TIMING_CONSTANTS as CONFIG_TIMING_CONSTANTS, MEMORY_CONSTANTS as CONFIG_MEMORY_CONSTANTS, CONTINUATION_CONSTANTS as CONFIG_CONTINUATION_CONSTANTS, ORCHESTRATOR_RESTART_CONSTANTS as CONFIG_ORCHESTRATOR_RESTART_CONSTANTS, AGENT_SUSPEND_CONSTANTS as CONFIG_AGENT_SUSPEND_CONSTANTS, VERSION_CHECK_CONSTANTS as CONFIG_VERSION_CHECK_CONSTANTS, AUTO_UPDATE_CONSTANTS as CONFIG_AUTO_UPDATE_CONSTANTS, CLOUD_DISCONNECT_NOTICE_CONSTANTS as CONFIG_CLOUD_DISCONNECT_NOTICE_CONSTANTS, AGENT_HEARTBEAT_MONITOR_CONSTANTS as CONFIG_AGENT_HEARTBEAT_MONITOR_CONSTANTS, ORCHESTRATOR_HEARTBEAT_CONSTANTS as CONFIG_ORCHESTRATOR_HEARTBEAT_CONSTANTS, MARKETPLACE_CONSTANTS as CONFIG_MARKETPLACE_CONSTANTS, TEMPLATE_MARKETPLACE_CONSTANTS as CONFIG_TEMPLATE_MARKETPLACE_CONSTANTS, ADDON_CONSTANTS as CONFIG_ADDON_CONSTANTS, AUDITOR_CONSTANTS as CONFIG_AUDITOR_CONSTANTS, PROCESS_EXIT_CODES as CONFIG_PROCESS_EXIT_CODES, SAFE_RESTART_CONSTANTS as CONFIG_SAFE_RESTART_CONSTANTS, WEB_CONSTANTS as CONFIG_WEB_CONSTANTS, API_SECURITY_CONSTANTS as CONFIG_API_SECURITY_CONSTANTS, } from '../../config/constants.js';
+import { CREWLY_CONSTANTS as CONFIG_CREWLY_CONSTANTS, AGENT_IDENTITY_CONSTANTS as CONFIG_AGENT_IDENTITY_CONSTANTS, TIMING_CONSTANTS as CONFIG_TIMING_CONSTANTS, MEMORY_CONSTANTS as CONFIG_MEMORY_CONSTANTS, CONTINUATION_CONSTANTS as CONFIG_CONTINUATION_CONSTANTS, ORCHESTRATOR_RESTART_CONSTANTS as CONFIG_ORCHESTRATOR_RESTART_CONSTANTS, AGENT_SUSPEND_CONSTANTS as CONFIG_AGENT_SUSPEND_CONSTANTS, VERSION_CHECK_CONSTANTS as CONFIG_VERSION_CHECK_CONSTANTS, AUTO_UPDATE_CONSTANTS as CONFIG_AUTO_UPDATE_CONSTANTS, CLOUD_DISCONNECT_NOTICE_CONSTANTS as CONFIG_CLOUD_DISCONNECT_NOTICE_CONSTANTS, AGENT_HEARTBEAT_MONITOR_CONSTANTS as CONFIG_AGENT_HEARTBEAT_MONITOR_CONSTANTS, ORCHESTRATOR_HEARTBEAT_CONSTANTS as CONFIG_ORCHESTRATOR_HEARTBEAT_CONSTANTS, MARKETPLACE_CONSTANTS as CONFIG_MARKETPLACE_CONSTANTS, TEMPLATE_MARKETPLACE_CONSTANTS as CONFIG_TEMPLATE_MARKETPLACE_CONSTANTS, ADDON_CONSTANTS as CONFIG_ADDON_CONSTANTS, AUDITOR_CONSTANTS as CONFIG_AUDITOR_CONSTANTS, PROCESS_EXIT_CODES as CONFIG_PROCESS_EXIT_CODES, SAFE_RESTART_CONSTANTS as CONFIG_SAFE_RESTART_CONSTANTS, WEB_CONSTANTS as CONFIG_WEB_CONSTANTS, API_SECURITY_CONSTANTS as CONFIG_API_SECURITY_CONSTANTS, PROJECT_TICKET_CONSTANTS as CONFIG_PROJECT_TICKET_CONSTANTS, } from '../../config/constants.js';
 // Re-export the cross-domain constants for backend use
 export const PROCESS_EXIT_CODES = CONFIG_PROCESS_EXIT_CODES;
+/** Project tickets (specs/2026-09-28-project-tickets.md) — see config/constants.ts. */
+export const PROJECT_TICKET_CONSTANTS = CONFIG_PROJECT_TICKET_CONSTANTS;
 /**
  * Safe restart: drain in-flight agent turns before a shutdown kills the PTYs,
  * and resume the ones that were cut off after the next boot.
@@ -247,6 +249,111 @@ export const PTY_CONSTANTS = {
      */
     ORPHAN_REAPER_INTERVAL_MS: 5 * 60 * 1000,
 };
+/**
+ * Control-plane guard for Claude Code agent sessions (Request 72c9427a,
+ * specs/2026-09-24-control-plane-isolation.md Part 3).
+ *
+ * The backend writes a per-session settings file (permissions.deny + a
+ * PreToolUse Bash hook) and passes it with `--settings`, so an agent cannot
+ * edit the files that stop, start and configure agents. All paths are
+ * relative to the root named by the group: CREWLY_HOME (`~/.crewly`), the
+ * install root (the Crewly package / checkout), or the agent's project path.
+ */
+export const CONTROL_PLANE_GUARD_CONSTANTS = {
+    /** Backend env var; `0` turns the guard off for every session launched by this backend. */
+    KILL_SWITCH_ENV: 'CREWLY_CONTROL_PLANE_GUARD',
+    /** Value of KILL_SWITCH_ENV that disables the guard. Any other value (or unset) keeps it on. */
+    KILL_SWITCH_OFF_VALUE: '0',
+    /** Directory under CREWLY_HOME that holds the generated per-session files. */
+    RUNTIME_DIR: 'runtime/control-plane',
+    /** Suffix of the generated Claude Code settings file (`<session><suffix>`). */
+    SETTINGS_FILE_SUFFIX: '.settings.json',
+    /** Suffix of the protected-paths list the Bash hook reads (`<session><suffix>`). */
+    PATHS_FILE_SUFFIX: '.paths',
+    /** The PreToolUse Bash hook, relative to the install root. */
+    HOOK_SCRIPT: 'config/hooks/control-plane-guard/pretooluse-bash.sh',
+    /** CLI flag the settings file is passed with. */
+    SETTINGS_FLAG: '--settings',
+    /** Claude Code tool the PreToolUse hook is attached to. */
+    HOOK_TOOL_MATCHER: 'Bash',
+    /**
+     * Write-protected directories under CREWLY_HOME (whole subtree).
+     *
+     * `teams` is deliberately NOT here (WorkItem 70e54fbc / #798 review):
+     * specs/2026-09-24-control-plane-isolation.md Part 2 protects only
+     * `teams/*\/config.json`, not the whole subtree. A team directory also
+     * holds `norms/`, `wiki/`, `prompts/`, `sops/` and `cron-tasks.json` —
+     * files agents write routinely (`remember`, `record-learning`,
+     * norm/SOP authoring, follow-up scheduling). Blanket-protecting `teams`
+     * would block all of that. See TEAM_CONFIG_FILE_NAME below for how the
+     * narrower rule is built (one entry per existing team, resolved at
+     * guard-prep time since the hook needs literal paths, not globs).
+     */
+    CREWLY_HOME_DIRS: ['triggers', 'runtime/control-plane'],
+    /**
+     * Directory under CREWLY_HOME holding one subdirectory per team, each
+     * expected to contain a `config.json` (see TEAM_CONFIG_FILE_NAME).
+     */
+    TEAMS_DIR_NAME: 'teams',
+    /** File name, within each team's directory, that the guard protects. */
+    TEAM_CONFIG_FILE_NAME: 'config.json',
+    /** Write-protected files under CREWLY_HOME. */
+    CREWLY_HOME_FILES: [
+        'recurring-checks.json',
+        'one-time-checks.json',
+        'scheduled-messages.json',
+        'settings.json',
+        'runtime-pids.json',
+        'session-state.json',
+        'api-token',
+    ],
+    /** Files under CREWLY_HOME that agents must not read with the built-in tools either. */
+    CREWLY_HOME_READ_DENIED_FILES: ['api-token'],
+    /** Write-protected directories under the install root (whole subtree). */
+    INSTALL_DIRS: [
+        'config/skills/orchestrator/stop-agent',
+        'config/skills/orchestrator/start-agent',
+        'config/skills/orchestrator/terminate-agent',
+        'config/skills/orchestrator/stop-team',
+        'config/skills/orchestrator/start-team',
+        'config/skills/orchestrator/restart-crewly',
+        'config/hooks/control-plane-guard',
+        // #815: the agent-status hook runs on every tool call; an agent must not
+        // be able to silence or rewrite it.
+        'config/hooks/agent-status',
+        'dist',
+    ],
+    /** Write-protected files under the install root. */
+    INSTALL_FILES: ['config/skills/_common/lib.sh'],
+    /** Write-protected directories under the agent's project path (whole subtree). */
+    PROJECT_DIRS: ['.claude/agents', '.crewly/triggers'],
+};
+/**
+ * Agent-status hook (#815, specs/2026-09-26-agent-waiting-on-human.md): Claude
+ * Code hook events that tell the backend when an agent waits on the user.
+ * Registered in the control-plane guard's per-session settings file, never as
+ * a second settings file, and never on PreToolUse (that event is the guard's).
+ */
+export const AGENT_STATUS_HOOK_CONSTANTS = {
+    /** Hook script, relative to the install root. */
+    HOOK_SCRIPT: 'config/hooks/agent-status/report.sh',
+    /** Hook events the script is registered for. */
+    EVENTS: ['Notification', 'PermissionRequest', 'Stop', 'UserPromptSubmit', 'PostToolUse'],
+    /** Events that carry a tool matcher; they match every tool. */
+    TOOL_EVENTS: ['PermissionRequest', 'PostToolUse'],
+    /** Matcher that selects every tool. */
+    ALL_TOOLS_MATCHER: '*',
+    /** Notification types that mean "waiting on the user". */
+    WAITING_NOTIFICATION_TYPES: ['permission_prompt', 'elicitation_dialog'],
+    /** Every notification type the endpoint accepts (others are rejected). */
+    KNOWN_NOTIFICATION_TYPES: ['permission_prompt', 'elicitation_dialog', 'idle_prompt', 'auth_success'],
+    /** Max length of an accepted event or notification-type identifier. */
+    MAX_IDENTIFIER_LENGTH: 64,
+    /** Sessions whose latest hook signal is kept in memory (oldest dropped past this). */
+    MAX_TRACKED_SESSIONS: 500,
+    /** Accepted X-Agent-Session header value. */
+    SESSION_NAME_PATTERN: /^[A-Za-z0-9._-]{1,128}$/,
+};
 /**
  * Session recreation (Step 2 full recreation in AgentRegistrationService).
  *
@@ -580,6 +687,44 @@ export const ACTIVITY_MONITOR_CONSTANTS = {
      *  (spinners, TUI re-renders). Default: 15 minutes. */
     MAX_IN_PROGRESS_MS: 900_000,
 };
+/**
+ * Give-up recovery (#841, specs/2026-09-27-give-up-recovery.md): when a worker
+ * stops on a feasibility give-up, queue a retry with a different approach,
+ * bounded per root WorkItem, then one escalation to the team lead.
+ */
+export const GIVE_UP_RECOVERY_CONSTANTS = {
+    /** Retries per root WorkItem when the team sets no recoveryPolicy. */
+    DEFAULT_MAX_RETRIES: 2,
+    /** Retry WorkItem id: `${rootId}${RETRY_ID_INFIX}${attempt}`. */
+    RETRY_ID_INFIX: ':giveup:',
+    /** Escalation review WorkItem id: `${rootId}${REVIEW_ID_SUFFIX}`. */
+    REVIEW_ID_SUFFIX: ':review:gave_up',
+    /** WorkItem.metadata key for the recorded stop classification. */
+    STOP_METADATA_KEY: 'stop',
+    /** WorkItem.metadata key for the attempt log carried by retries. */
+    GIVE_UP_METADATA_KEY: 'giveUp',
+    /** Characters of stop text kept per attempt. */
+    MAX_REASON_CHARS: 2000,
+    /** Audit label for transitions this feature makes. */
+    ACTOR_VIA: 'give-up-recovery',
+};
+/**
+ * Constants for the waiting_on_human attention verdict (#815).
+ * See specs/2026-09-26-agent-waiting-on-human.md.
+ */
+export const AGENT_ATTENTION_CONSTANTS = {
+    /** Non-empty lines at the bottom of the screen the dialog rules examine.
+     *  Dialogs render at the bottom; older answered dialogs sit above it. */
+    BOTTOM_LINES: 20,
+    /** Lines captured from the terminal buffer for the verdict (more than the
+     *  5 lines the activity diff uses, because a dialog spans ~15 lines). */
+    CAPTURE_LINES: 60,
+    /** How long an agent must stay waiting_on_human before the reconciler moves
+     *  its running WorkItems to blocked (5 minutes). */
+    BLOCK_WORK_ITEM_AFTER_MS: 300_000,
+    /** WorkItem blockedReason / escalation reason used for this state. */
+    BLOCKED_REASON: 'waiting_on_human',
+};
 /**
  * Event bus constants for the agent event pub/sub system.
  * Used by EventBusService for subscription management and notification delivery.
@@ -701,6 +846,94 @@ export const WIKI_KB_CONSTANTS = {
     /** Frontmatter keys agents may set. */
     FRONTMATTER_KEYS: ['title', 'summary', 'keep_because', 'tags', 'visibility', 'source', 'caller', 'recorded', 'updated', 'superseded_by', 'superseded_at', 'superseded_reason', 'proposed_by'],
 };
+/**
+ * Standing-answer pages (#816): a few question-anchored pages per scope,
+ * read at boot as a plain file read (no retrieval, no LLM) and refreshed by
+ * an agent only when the memory behind them has moved.
+ */
+export const STANDING_ANSWERS_CONSTANTS = {
+    /** Project pages live here, under the project's `.crewly` data dir. */
+    PROJECT_DIR: 'wiki/llm-curated/standing',
+    /** The agent page, under `<CREWLY_HOME>/agents/<session>/`. */
+    AGENT_FILE: 'standing.md',
+    /** Page id of the agent page. */
+    AGENT_PAGE_ID: 'unfinished-work',
+    /** Hard cap on the whole Standing Answers prompt section (~2 000 tokens). */
+    PROMPT_MAX_CHARS: 8000,
+    /** Cap on one page's body inside the prompt. */
+    PROMPT_PAGE_MAX_CHARS: 3000,
+    /** Cap on one section body written through the API. */
+    SECTION_MAX_CHARS: 1500,
+    /** Cap on a section heading. */
+    HEADING_MAX_CHARS: 80,
+    /** Cap on citations per section. */
+    MAX_CITES_PER_SECTION: 20,
+    /** Entries listed in a refresh WorkItem brief. */
+    BRIEF_MAX_ENTRIES: 30,
+    /** Characters of each entry shown in a refresh brief. */
+    BRIEF_ENTRY_MAX_CHARS: 240,
+    /** Refresh tick interval when CREWLY_WIKI_REFLECT_INTERVAL_MS is unset (the reflect default). */
+    REFRESH_INTERVAL_MS: 60 * 60 * 1000,
+    /** Minimum time between two refresh WorkItems for the same page. */
+    REFRESH_COOLDOWN_MS: 6 * 60 * 60 * 1000,
+    /** At most this many refresh WorkItems per tick (PTY paste-flood guard). */
+    REFRESH_MAX_CREATES_PER_TICK: 2,
+    /**
+     * A refresh WorkItem that failed or was cancelled without writing the page
+     * is retried even though the source watermark has not moved again (it
+     * otherwise would not be re-raised until new memory arrives). Bounded so a
+     * page that keeps failing does not retry forever.
+     */
+    REFRESH_MAX_RETRIES: 2,
+    /** Refresh bookkeeping (last raised watermark per page), under CREWLY_HOME. */
+    REFRESH_STATE_FILE: 'standing-refresh-state.json',
+    /** `metadata.kind` of refresh WorkItems. */
+    WORKITEM_KIND: 'standing-refresh',
+    /**
+     * Decisions whose title starts with this are task-completion records that
+     * report-status files automatically, not decisions; they are out of scope
+     * for "decisions in force" (in this repo: 229 of 327 decision entries).
+     */
+    COMPLETED_DECISION_PREFIX: '[COMPLETED]',
+    /**
+     * Agent-memory entries starting with this are report-status completion
+     * learnings ("Task completed: <summary>"). Done work is neither
+     * unfinished nor blocking, so they are out of scope for the agent page
+     * and do not move its watermark; "Task failed:"/"Task blocked:" stay in.
+     */
+    COMPLETED_LEARNING_PREFIX: 'Task completed:',
+};
+/**
+ * Per-WorkItem git worktrees (#814). Opt-in per project in v1
+ * (`Project.worktrees = 'on'`); a team can opt out (`Team.worktrees =
+ * 'off'`); `CREWLY_WORKTREES=off` disables them everywhere.
+ */
+export const WORKTREE_CONSTANTS = {
+    /** Worktrees live here, relative to the repo root (gitignored via .crewly). */
+    DIR: '.crewly/worktrees',
+    /** Per-worktree manifests (symlinks, copies, base) live here, inside DIR. */
+    META_DIR: '.meta',
+    /** Branch name prefix: `wi/<workItemId>`. */
+    BRANCH_PREFIX: 'wi/',
+    /** Repo-root file listing gitignored-but-needed files to copy in. */
+    INCLUDE_FILE: '.worktreeinclude',
+    /** Cap on `.worktreeinclude` entries honoured. */
+    INCLUDE_MAX_ENTRIES: 50,
+    /** Heavy directories symlinked (not copied) from the repo root when present and untracked. */
+    DEFAULT_SHARED_DIRS: ['node_modules'],
+    /** Marker line for the entries this feature adds to `.git/info/exclude`. */
+    EXCLUDE_MARKER: '# crewly worktree shared paths (#814) — never commit these',
+    /** Timeout for local git commands (checkout of a large repo can take minutes under load). */
+    GIT_TIMEOUT_MS: 10 * 60 * 1000,
+    /** Timeout for `git ls-remote` (offline must not hang the sweep). */
+    REMOTE_TIMEOUT_MS: 15_000,
+    /** Orphan sweep interval. */
+    SWEEP_INTERVAL_MS: 30 * 60 * 1000,
+    /** Kill switch env var; the value `off` disables worktrees everywhere. */
+    ENV_KILL_SWITCH: 'CREWLY_WORKTREES',
+    /** WorkItem metadata key holding the worktree record. */
+    METADATA_KEY: 'worktree',
+};
 /** How many recent thread channels an owner notification tries before giving up when SLACK_DEFAULT_CHANNEL is unset. */
 export const SLACK_NOTIFICATION_FALLBACK_MAX_CANDIDATES = 4;
 /**
@@ -1420,7 +1653,15 @@ export const FRESH_TASK_CONVERSATION_CONSTANTS = {
     ENV_TOGGLE: 'CREWLY_FRESH_TASK_CONVERSATION',
     /** Under CREWLY_HOME: `{ [session]: lastDeliveredRootId }` */
     STATE_FILE: 'fresh-task-conversation.json',
-    /** Id suffixes that mark follow-ups of the same task (retries, verifies, reviews) */
+    /**
+     * Id suffixes that mark follow-ups of the same task (retries, verifies,
+     * reviews). Deliberately excludes give-up recovery's `:giveup:N` (#841,
+     * #843): a give-up retry is meant to be a materially DIFFERENT approach,
+     * and its WorkItem description already carries the full attempt log, so
+     * nothing is lost by treating it as a new root — the agent starts that
+     * retry with a fresh conversation instead of one anchored on the
+     * reasoning that just failed. See give-up-recovery.service.ts buildRetry.
+     */
     ROOT_SUFFIX_MARKERS: [':retry:', ':verify:', ':review:'],
     /** The Claude Code command that starts a new conversation */
     CLEAR_COMMAND: '/clear',
@@ -1448,6 +1689,44 @@ export const FRESH_TASK_CONVERSATION_CONSTANTS = {
     MEMORY_MAX_CHARS: 4_000,
     /** Members start fresh at launch when their last turn carried this many tokens. Env: CREWLY_MEMBER_FRESH_CONTEXT_TOKENS */
     MEMBER_FRESH_CONTEXT_TOKENS: 150_000,
+    /**
+     * Idle-boundary context cap: a Claude Code member (never the orchestrator)
+     * whose last turn carried more than this many tokens is saved (handover +
+     * wiki) and cleared between turns, then re-oriented on its WorkItem. One
+     * long task can otherwise run 1000+ turns at 650k–965k context.
+     */
+    MEMBER_CONTEXT_CAP_TOKENS: 300_000,
+    /** Env override for {@link MEMBER_CONTEXT_CAP_TOKENS}; `0` disables the cap */
+    MEMBER_CONTEXT_CAP_ENV: 'CREWLY_MEMBER_CONTEXT_CAP_TOKENS',
+    /** At most one context-cap clear per session in this window */
+    CONTEXT_CAP_MIN_INTERVAL_MS: 20 * 60_000,
+    /**
+     * The PTY must have been quiet this long before a context-cap clear —
+     * longer than {@link MIN_QUIET_MS} because nothing is waiting on it and a
+     * turn that merely paused must not be cut.
+     */
+    CONTEXT_CAP_MIN_QUIET_MS: 30_000,
+    /** How often the context-cap sweep checks members */
+    CONTEXT_CAP_SWEEP_MS: 60_000,
+    /** Tag on the re-orientation line written after a context-cap clear */
+    CONTEXT_CAP_TAG: '[CREWLY-CONTEXT-CAP]',
+};
+/**
+ * Cooperation between a direct task hand-over (team-leader delegate-task:
+ * `/task-pool/add`, then `/terminal/:s/deliver` with the full brief) and the
+ * WorkItem dispatcher's `workitem:queued` push, so a task reaches its agent
+ * once and the fresh-conversation clear happens once, before that delivery.
+ */
+export const DIRECT_DELIVERY_CONSTANTS = {
+    /** WorkItem metadata flag set by callers that deliver the task text themselves */
+    METADATA_FLAG: 'directDelivery',
+    /**
+     * How long the dispatcher holds off a `workitem:queued` push for a
+     * direct-delivery WorkItem. Covers the delegate-task ladder: deliver
+     * (15 s ready wait) → force → auto-start + 10 s + deliver (30 s). After
+     * this, if nobody delivered it, the dispatcher pushes its brief.
+     */
+    GRACE_MS: 90_000,
 };
 /**
  * Default model for Claude Code team members that have no `modelId`: members
@@ -2878,6 +3157,33 @@ export const SELF_IMPROVEMENT_CONSTANTS = {
         INACCURATE: ['incorrect', 'inaccurate', 'false', 'no', 'wrong', 'missed'],
     },
 };
+/**
+ * Daily owner receipt (#828): one phone-readable message every evening with
+ * every ask of the window, its outcome and link, what waits on the owner, and
+ * what it cost. See specs/owner-receipt.md.
+ */
+export const OWNER_RECEIPT_CONSTANTS = {
+    /** Default local send time (HH:MM, 24h) */
+    DEFAULT_TIME: '21:00',
+    /** Default owner time zone (same default as team-health off-hours) */
+    DEFAULT_TIMEZONE: 'America/New_York',
+    /** How often the scheduler checks whether it is time (ms) */
+    TICK_INTERVAL_MS: 60 * 1000,
+    /** Settings + last-sent state, under ~/.crewly */
+    STATE_FILENAME: 'owner-receipt.json',
+    /** An ask is shortened to this many characters (CJK count double) */
+    MAX_ASK_WEIGHTED_LENGTH: 56,
+    /** A waiting-on-you question is shortened to this many characters */
+    MAX_QUESTION_WEIGHTED_LENGTH: 90,
+    /** Ask lines in the Slack message before "另有 N 件" (phone length) */
+    MAX_ASK_LINES: 30,
+    /** Waiting-on-you lines before "另有 N 件" */
+    MAX_WAITING_LINES: 12,
+    /** 「可能漏记」 lines: appended messages that still read like a request (#828 coverage) */
+    MAX_POSSIBLY_MISSED: 5,
+    /** Team label for a ticket nobody is assigned to */
+    UNASSIGNED_TEAM: '未分配',
+};
 /**
  * Ticket loop (specs/ticket-loop.md, Phase 1): owner messages become tickets
  * (a `Request` with a TKT number), receipts go back where the owner spoke,
@@ -2890,6 +3196,13 @@ export const TICKET_CONSTANTS = {
     NUMBER_PAD: 3,
     /** Counter file inside the requests dir (no `.json`, so listAll never reads it) */
     COUNTER_FILENAME: '.ticket-counter',
+    /**
+     * #828 coverage: one JSON line per owner message intake handled
+     * (created / appended / ignored + reason), next to the Request files. The
+     * first line records when counting started, so a window that begins
+     * earlier is reported as unknown (不详), never as 0.
+     */
+    INTAKE_LOG_FILENAME: '.intake-outcomes.jsonl',
     /** Tag every ticket carries */
     TAG: 'ticket',
     /** Tag added when the owner said "don't track" */
@@ -2900,8 +3213,81 @@ export const TICKET_CONSTANTS = {
      * (7 CJK = 14), while "好的收到" (8) does not.
      */
     MIN_WEIGHTED_TEXT_LENGTH: 12,
+    /** Tag on a ticket an agent split out of another (#827) */
+    SPLIT_TAG: 'split',
     /** A bare "don't track" reply dismisses the ticket it answers */
     DISMISS_PATTERN: /^\s*(不用记|别记|不用记录|不要记|取消记录|don'?t track|do not track|no ticket)\s*[。.!！]*\s*$/i,
+    /**
+     * Ask classifier (#827): is an owner message a new ask, or a follow-up on
+     * the thread's current deliverable? Deterministic, text only. Every
+     * pattern below was taken from real owner messages of 2026-09-25/26 — see
+     * ticket-ask-classifier.test.ts for the labelled set. Scoring and the
+     * tie rule live in ticket-ask-classifier.ts.
+     */
+    ASK: {
+        /** A request verb: something to go and do (+2 ask) */
+        REQUEST_VERB: /(研究|调研|查一下|查查|搜一下|搜索一下|搜搜|搜一搜|找一下|找找|(看看|看一下|看下)(?!上面|这个|吧|吗|嘛|呢|[？?。!！~]|\s*$)|了解一下|分析一下|深挖|挖一下|总结|汇总|对比|比较一下|开\s*(个|一个|几个)?\s*issues?|提\s*(个|一个)?\s*issues?|发给|发到|做成|生成|加到|添加|帮我|帮忙|给我(讲讲|发|找|整理|列)|给我看看\S|告诉我|按\s*\S{1,12}\s*(分组|归类|group)|\bgroup\b|让\S{1,12}去|monitor|盯一下|提醒我|跑一下|部署|\bresearch\b|look into|dig into|find out|summari[sz]e|\bcompare\b|(open|file|create)\s+(the\s+\S+\s+to\s+)?(an?\s+|github\s+)?issues?|github issues?|write (up|a |an )|\bdraft\b|tell me|explain)/i,
+        /**
+         * An explicit request construction (+3 ask instead of +2). Survives the
+         * long-discussion damping: 「你能不能帮我…总结成一个MD文档」 inside a
+         * voice transcript is still an ask.
+         */
+        STRONG_REQUEST: /(你能不能帮我|能不能帮我|你能帮我|我希望你|希望.{0,4}你们?(能|可以)|我建议你|需要你去|(?<!谢谢)你帮我(?!\s*draft)|帮我把|创建对应的|创建一个)/,
+        /** A question that asks for information (+1 ask; on its own, a question ticket) */
+        INFO_QUESTION: /(是什么|什么意思|是讲什么|讲的是什么|是啥|怎么回事|区别|有什么值得|有什么可以|能有什么|有哪些|都有什么|有几个|有多少|有没有|what is|what's|what does|what even|how does|how do)/i,
+        /** The message points at something to look at: a link, an image, a file path */
+        REFERENCE: /(https?:\/\/|\[Slack (Image|File):|[\w-]+\/[\w./-]+\.(md|pdf|png|jpe?g))/i,
+        /** A bare 「看看」 (look) — an ask only when it has a reference to look at */
+        LOOK: /(看看|看一下|看下|看一看)/,
+        /** Opens a new topic, near the start (+1 ask) */
+        NEW_TOPIC: /^.{0,6}(另外|还有一个|还有个|另一个|新的想法|有一个新的|对了)/,
+        /** Suggests something new to do (+1 ask) */
+        IDEA: /(我们(crewly)?也可以|我们可以|要不(要)?|不如|可以考虑)/i,
+        /** First line is a numbered reply to the agent's list (+3 follow) */
+        NUMBERED_REPLY: /^\s*(1[.、)）]|1\s|1和|关于1|①)/,
+        /**
+         * How the CURRENT deliverable should be delivered (+3 follow). Needs a
+         * delivery verb: a bare `00-plan.md` path is not an instruction.
+         */
+        DELIVERY_FORMAT: /((发|给我|存|转|用|通过|做成).{0,6}(pdf|md|markdown)|存到|写到.{0,20}(md|文档|issue)|放到|preview|文字稿)/i,
+        /** Clarifies or corrects the work in progress (+2 follow) */
+        CLARIFY: /(我只是|我的意思|我是说|除非你|不是说|不是让你|就是说|没关系|算了|先不|先留|backlog|后面再|以后再|不着急|不用了|不需要|等一下|按你说的|你决定|你来定|你们来定|请你们来|主要是)/,
+        /** Feedback on the current draft (+3 follow) */
+        FEEDBACK: /(基本上?可以|整体看?可以|还可以再|再斟酌|打磨|少了|多了|改成|改一下|基本对)/,
+        /** Asks the agent about its own work or plan (+2 follow) */
+        ABOUT_AGENT_WORK: /(你打算|你觉得|你有数|你看到|你去调研的时候|你那边|你有什么想法|你是怎么|你怎么|你有吗|我前面问|之前问|前面说了|再问一次)/,
+        /**
+         * Opens by correcting or choosing (+3 follow): 「不对 我要你研究的是…」,
+         * 「不是前面…」, 「方案A」 — a reply to the agent, never a new ask.
+         */
+        CORRECTION_OR_CHOICE: /^(不对|不是|不用|sorry|方案\s*[A-Za-z0-9一二三]|选\s*[A-Za-z0-9一二三]|[A-Da-d][。.，,\s]|按推荐|按你推荐)/i,
+        /** 「…给我看看吗」: show me the current thing (+3 follow) */
+        SHOW_ME_TAIL: /给我看看?[吗嘛呢？?\s]*$/,
+        /** Retry / continue the current work (+3 follow): 「你再看看」「按你说的继续挖」 */
+        RETRY_CONTINUE: /(再看看|再看一次|再试试|你再|重新|继续|接着)/,
+        /** Ends as a suggestion about the current work (+3 follow): 「…添加一些截图吧？」 */
+        SUGGEST_TAIL: /吧[？?]?\s*$/,
+        /** Asks where things stand (+3 follow; top level: not an ask) */
+        STATUS_PING: /(在线了吗|好了吗|怎么样了|现在呢|有听吗|进展|进度|到哪了|有数了吗|登陆了吗|登陆过了|在吗|done yet|any update|how'?s it going|\bstatus\b|right now|working on)/i,
+        /**
+         * A line that approves what the agent proposed: starts with an ack and
+         * ends in approval ("好的 开issue可以的", "好的 部署吧") (+3 follow)
+         */
+        APPROVAL_LINE: /^(好的?|行|可以|ok|okay|嗯+|对|对的|没问题|挺好的?)[\s，,。!！]*(\S.{0,24}?(可以的?|就行|没问题|吧)[\s。!！~]*)?$/i,
+        /** A line that is only an acknowledgement (ignored when scoring the rest) */
+        ACK_ONLY_LINE: /^(好的?|行|可以|ok|okay|嗯+|对|对的|没问题|挺好的?|收到|谢谢|thx|thanks)[\s，,。!！~]*$/i,
+        /**
+         * Weighted length above which a message reads as spoken discussion (a
+         * voice transcript): a follow-up unless it opens a new topic (+2 follow)
+         */
+        LONG_DISCUSSION_WEIGHTED_LENGTH: 300,
+        /** Ends like a question (a verb-less question in a thread needs one) */
+        QUESTION_MARK: /([？?吗呢]|是什么|什么意思|是啥|的区别是什么)\s*$/m,
+        /** Quoted text is content, not a request: 接住“能不能帮我做” asks nothing */
+        QUOTED: /“[^”]*”|「[^」]*」|"[^"]*"/g,
+        /** Minimum ask score for a new ask; it must also beat the follow score (ties append) */
+        MIN_ASK_SCORE: 2,
+    },
     /**
      * A top-level "不用记" (no thread) dismisses the latest open ticket from the
      * same conversation if it was opened this recently (ms).