test-task: recall check reads the wrong record, vacuous identity check, docker info vs compose #1541

Open
opened 2026-10-10 08:55:30 +00:00 by jarvis · 0 comments
Contributor

Follow-up from row 48 (#1534): checks in scripts/test-task.sh that can pass or report for the wrong reason. Row 48's brief left the recall check's content out of scope. None of these blocked the row.

Sources: Dewey's packet (agents/dewey/work/queue-48/evidence.md, "Follow-ups"), Darkwing's verdict (27099, notes 2 and 3), Filbert's verdict (27100, N3).

  1. The name check reads someone else's run record. FR="$(ls -dt "$SANDBOX/data/runs"/r-* | head -1)" takes the newest record whether or not the recall run wrote one. In Dewey's mutant the check failed but printed the fork child's response (mosaico). Pick the record the recall run wrote, for example by run id from its output, and fail with a clear message when there isn't one.
  2. "no agent identity on headless run" passes vacuously. ! grep -q 'AGENT IDENTITY' "$SANDBOX/data/system-prompt.md" 2>/dev/null is true when the file is absent. Darkwing's fake-Docker run printed OK after a run that never started. Require the file to exist before checking what it lacks.
  3. The Docker guards ask docker info, but the runs use docker compose run (Darkwing note 2). A host with the daemon and no compose plugin fails the live blocks instead of skipping them. All four guards (lines 139, 395, 442 and the recall pair) share it. Decide whether the guard should test compose too.

Owner: unassigned, not queued yet. Reviewers when queued: Darkwing and Filbert.

Follow-up from row 48 (#1534): checks in `scripts/test-task.sh` that can pass or report for the wrong reason. Row 48's brief left the recall check's content out of scope. None of these blocked the row. Sources: Dewey's packet (`agents/dewey/work/queue-48/evidence.md`, "Follow-ups"), Darkwing's verdict (27099, notes 2 and 3), Filbert's verdict (27100, N3). 1. The name check reads someone else's run record. `FR="$(ls -dt "$SANDBOX/data/runs"/r-* | head -1)"` takes the newest record whether or not the recall run wrote one. In Dewey's mutant the check failed but printed the fork child's response (`mosaico`). Pick the record the recall run wrote, for example by run id from its output, and fail with a clear message when there isn't one. 2. "no agent identity on headless run" passes vacuously. `! grep -q 'AGENT IDENTITY' "$SANDBOX/data/system-prompt.md" 2>/dev/null` is true when the file is absent. Darkwing's fake-Docker run printed `OK` after a run that never started. Require the file to exist before checking what it lacks. 3. The Docker guards ask `docker info`, but the runs use `docker compose run` (Darkwing note 2). A host with the daemon and no compose plugin fails the live blocks instead of skipping them. All four guards (lines 139, 395, 442 and the recall pair) share it. Decide whether the guard should test compose too. Owner: unassigned, not queued yet. Reviewers when queued: Darkwing and Filbert.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: mosaicstack/stack#1541