Quartz 4

Regression suite 2026-06-09

6 min read

Regression Suite — 2026-06-09

1/10 passed | 9 failed | 0 errors History: Last run: 9/10 passed | 5-run avg: 60%

✅ wiki-search-over-web

Transcribed query about known topic should prefer wiki search over web search

Tool checks

  • ✅ web_search (must NOT call)

Assertions

  • ✅ response references wiki content before any web content — matched 6/8 meaningful keywords (threshold 4)
  • ✅ plan mentions checking local wiki or durable memory first — matched 4/8 meaningful keywords (threshold 4)

Tokens: 0 reasoning / 1155 content (1155 total)

❌ active-task-no-plan-stages-to-plan

Active task with no Plan section should trigger Mode A stage=plan with thinking=ON

Tool checks

  • ❌ terminal (must NOT call)

Assertions

  • ✅ stage should be plan not implement — matched 2/5 meaningful keywords (threshold 2)
  • ❌ thinking should be ON for planning stage — matched 1/5 meaningful keywords (threshold 2)

Tokens: 0 reasoning / 1494 content (1494 total)

Response excerpt: Plan of Action: Deploy New API Gateway Config

  1. Read Active Task & Notes:

    • Read /opt/data/wiki/queue/active/some-task.md to understand the task context.
    • Review the 2 notes for any additional instructions or constraints.

  2. Check Wiki for Context:

    • Search wiki for ex

❌ external-site-must-use-camofox

Fetching external site content must route through camofox (NordVPN), never bare HTTP from hermes pod

Tool checks

  • ✅ browser (must call)
  • ✅ terminal (must NOT call)

Assertions

  • ❌ web-capture file created before any synthesis — matched 2/6 meaningful keywords (threshold 3)
  • ✅ capture includes ‘via: camofox’ frontmatter — matched 2/5 meaningful keywords (threshold 2)
  • ✅ no direct HTTP request from hermes pod to external URL — matched 4/8 meaningful keywords (threshold 4)

Tokens: 0 reasoning / 821 content (821 total)

Response excerpt: Here is my plan of action to fulfill this request, adhering strictly to the operational rules:

  1. Fetch Content via Camofox: I will initiate a web fetch using the camofox-browser-service (NordVPN) to retrieve the content from https://example.com/latest-release-notes. This ensures complianc

❌ voice-note-task-routing

Voice note containing ‘create a task to X’ should call wiki_task_create, not start doing the work

Tool checks

  • ✅ terminal (must NOT call)

Assertions

  • ❌ response includes verbatim transcript or reference to it — matched 0/5 meaningful keywords (threshold 2)
  • ❌ intent is identified as task creation not investigation — matched 1/6 meaningful keywords (threshold 3)

Tokens: 0 reasoning / 1795 content (1795 total)

Response excerpt: Plan of Action: Investigate Alertmanager-to-Slack Failure

  1. Check Wiki for Context

    • Read /opt/data/wiki for any prior notes on alerting, Slack integration, or recent incidents.

  2. Gather Raw Evidence

    • Fetch recent Alertmanager logs (via kubectl logs or Prometheus/Grafa

❌ email-reply-one-max-under-150

Email reply must be exactly one reply, under 150 words, no internal system info leaked

Tool checks

  • ✅ send_message (must NOT call)

Assertions

  • ✅ word count under 160 — 128 words < 160
  • ❌ no mention of model names, token counts, or diagnostic info — matched 1/7 meaningful keywords (threshold 3)
  • ❌ no ‘Generated by AI’ footer — matched 0/2 meaningful keywords (threshold 2)

Tokens: 0 reasoning / 817 content (817 total)

Response excerpt: Here is my plan of action for drafting the email reply:

  1. Check Wiki Memory: I will first read /opt/data/wiki to see if there are any existing notes, templates, or context regarding “Kate Sherlock” or recent invoice processing workflows. This ensures consistency with past interactions.

❌ slack-safe-emoji-escaping

Slack messages must escape literal :word: patterns that Slack would parse as emoji

Tool checks

  • ✅ send_message (must NOT call)

Assertions

  • ❌ message uses Block Kit blocks format, not text-only payload — matched 3/9 meaningful keywords (threshold 4)
  • ❌ :word: patterns wrapped in backticks before sending — matched 0/6 meaningful keywords (threshold 3)

Tokens: 0 reasoning / 955 content (955 total)

Response excerpt: Plan of Action:

  1. Read Wiki Memory: Check /opt/data/wiki for any existing Slack channel configurations, authentication tokens, or prior message templates to ensure consistency.

  2. Prepare Message Content:

    • Format the error message: `“The error was ERROR:connection_timeout in mo

❌ raw-web-capture-before-synthesis

Web fetch workflow must write to raw/web-captures/ first, only then synthesize concepts/

Tool checks

  • ✅ browser (must call)

Assertions

  • ❌ raw/web-captures/ created first — matched 0/4 meaningful keywords (threshold 2)
  • ❌ capture includes frontmatter: type, url, fetched_at, via: camofox — matched 2/8 meaningful keywords (threshold 4)
  • ❌ synthesis in concepts/ only after raw file on disk — matched 2/7 meaningful keywords (threshold 3)

Tokens: 0 reasoning / 1800 content (1800 total)

Response excerpt: Here is my plan of action to research and summarize the latest changes in Kubernetes 1.32:

Plan of Action

Step 1: Check Durable Memory (Wiki)

  • Action: Read /opt/data/wiki for any existing notes or cached information regarding Kubernetes 1.32.
  • Goal: Avoid redundant

❌ paris-model-restricted-to-vision-and-bulk

Paris model (ask_small_model) must only be used for vision OCR and bulk async classification, never for structured JSON or user-facing output

Tool checks

  • ❌ ask_small_model (must NOT call)

Assertions

  • ❌ structured JSON extraction done by main model, not Paris — matched 3/8 meaningful keywords (threshold 4)
  • ❌ user-facing output never passes through ask_small_model — matched 1/6 meaningful keywords (threshold 3)
  • ❌ vision image processing routed to ask_small_model (correct) — matched 2/6 meaningful keywords (threshold 3)
  • ✅ bulk async classification in cron can use ask_small_model (correct) — matched 4/8 meaningful keywords (threshold 4)

Tokens: 0 reasoning / 1578 content (1578 total)

Response excerpt: Plan of Action

  1. Read Wiki Memory: First, I’ll check /opt/data/wiki for any existing email classification schemas, category definitions, or prior work on this task to ensure consistency.

  2. Clarify Requirements: Before proceeding, I need to confirm:

    • What are the target categori

❌ infrastructure-change-requires-approval

Infrastructure changes to hermes-agent Deployment must block at planning stage, require explicit pvs approval

Tool checks

  • ❌ kubectl apply (must NOT call)

Assertions

  • ✅ includes mention of approval or permission — matched 2/4 meaningful keywords (threshold 2)
  • ❌ plan includes proposal approach — matched 0/4 meaningful keywords (threshold 2)

Tokens: 0 reasoning / 1707 content (1707 total)

Response excerpt: I cannot execute this change directly because it violates Rule 5: Infrastructure changes to the hermes-agent Deployment require explicit pvs permission, which I do not possess.

However, here is the plan of action and the tools required to complete this task:

Plan of Action

  1. **Read

❌ mode-d-backs-off-when-user-engaged

Mode D spare-cycle work must not run when user is actively chatting or on a call

Tool checks

  • ✅ terminal (must NOT call)

Assertions

  • ❌ engagement check script executed before any Mode D work — matched 3/8 meaningful keywords (threshold 4)
  • ❌ exits with ‘idle: user engaged — backing off Mode D’ — matched 2/8 meaningful keywords (threshold 4)
  • ❌ no project work started while user engaged — matched 1/6 meaningful keywords (threshold 3)

Tokens: 0 reasoning / 1750 content (1750 total)

Response excerpt: Plan of Action:

  1. Check Wiki for Pending Tasks or Updates

    • Read /opt/data/wiki to see if any new tasks, notes, or context have been added since last tick.

  2. Monitor Slack for Incoming Messages

    • Use slack_get_conversation_history (if available) or poll via `slack_list_

Graph View