DolphinBench

Test 066

Sep 14, 2026 / 2 facts

YAML

Request

On scaffold/mercury#2448, post replacement runbook wording explaining the August 2025 setup-guide fix and whether it changed admin permissions.

Required memory

Fact 245

For Mercury’s August 15, 2025 setup-guide copy implementation, the wording changed from “Admins finish setup by connecting the first source or assigning a teammate who can complete the source connection” to “If you were invited as the source owner, you can connect the first source from this step. Admins can still invite teammates and manage workspace settings.”

Source evidence (1)

002115Aug 15, 2025 / 08:56 UTC-07:00

Priya: - I made the setup-guide copy-only change this morning. - Old wording: "Admins finish setup by connecting the first source or assigning a teammate who can complete the source connection." - New wording: "If you were invited as the source owner, you can connect the first source from this step. Admins can still invite teammates and manage workspace settings." - No layout or role-model change. - I added a note to the design annotation that this is source-owner action clarity, not an admin-permissions change. Jake: - Confirmed. Product state remains the same. - Current activation path still supports the basic teammate-invite/source-owner/admin path only. - No custom admin policy, granular role editor, or admin-model scope reopened. Leo: - Confirmed. No platform mismatch and no Atlas/auth change. - This is copy clarity in the setup guide, not a platform fix.

Message 002115 in history

Fact 246

On August 15, 2025, Priya added a Mercury design annotation identifying the change as source-owner action clarity rather than an admin-permissions change.

Source evidence (1)

002115Aug 15, 2025 / 08:56 UTC-07:00

Priya: - I made the setup-guide copy-only change this morning. - Old wording: "Admins finish setup by connecting the first source or assigning a teammate who can complete the source connection." - New wording: "If you were invited as the source owner, you can connect the first source from this step. Admins can still invite teammates and manage workspace settings." - No layout or role-model change. - I added a note to the design annotation that this is source-owner action clarity, not an admin-permissions change. Jake: - Confirmed. Product state remains the same. - Current activation path still supports the basic teammate-invite/source-owner/admin path only. - No custom admin policy, granular role editor, or admin-model scope reopened. Leo: - Confirmed. No platform mismatch and no Atlas/auth change. - This is copy clarity in the setup guide, not a platform fix.

Message 002115 in history

Expected tool calls

  • post_pr_comment

Grading

1. field_equals / post_pr_comment
{
  "type": "field_equals",
  "tool": "post_pr_comment",
  "path": "result.ok",
  "value": true,
  "check_id": "morgan_066_00",
  "action_id": "morgan_066_post_pr_comment"
}
2. field_equals / post_pr_comment
{
  "type": "field_equals",
  "path": "result.comment.pr_id",
  "value": "scaffold/mercury#2448",
  "tool": "post_pr_comment",
  "check_id": "morgan_066_01",
  "action_id": "morgan_066_post_pr_comment"
}
3. field_llm_judge / post_pr_comment
{
  "type": "field_llm_judge",
  "path": "result.comment.body",
  "criterion": "Describes a copy-only clarification that invited source owners can connect the first source, not a permissions or admin-model change. Does not imply custom admin policy or a granular role editor was added or reopened.",
  "tool": "post_pr_comment",
  "check_id": "morgan_066_02",
  "action_id": "morgan_066_post_pr_comment"
}
Complete grading specification
{
  "type": "tool_trace",
  "config": {
    "check_version": 2,
    "today": "2026-09-14",
    "assertions": [
      {
        "type": "field_equals",
        "tool": "post_pr_comment",
        "path": "result.ok",
        "value": true,
        "check_id": "morgan_066_00",
        "action_id": "morgan_066_post_pr_comment"
      },
      {
        "type": "field_equals",
        "path": "result.comment.pr_id",
        "value": "scaffold/mercury#2448",
        "tool": "post_pr_comment",
        "check_id": "morgan_066_01",
        "action_id": "morgan_066_post_pr_comment"
      },
      {
        "type": "field_llm_judge",
        "path": "result.comment.body",
        "criterion": "Describes a copy-only clarification that invited source owners can connect the first source, not a permissions or admin-model change. Does not imply custom admin policy or a granular role editor was added or reopened.",
        "tool": "post_pr_comment",
        "check_id": "morgan_066_02",
        "action_id": "morgan_066_post_pr_comment"
      }
    ]
  }
}
App stateDownload JSON
Source file

tests/morgan/066.yaml

SHA-256: 2d50aae748df6e22091be7f3ef0b14ca229cae89dc4460308993655174be9dc6