Frontier model A

Trial · n0-slack-history-mirror

← n0-slack-history-mirror
Outcome
FAIL3m
Reward
0.0%
Checks passed
24 / 25
Runtime
3m 26s
Harness
Cursor CLI
Task version
v3.1.0

Checks

CheckResultCreditWeight
baseline: the sync job publishes Slack documentsPASS100%1%
baseline: the MCP server reads a published Slack documentPASS100%1%
refetch: a new or edited top-level post rebuilds its month without fetching any repliesPASS100%9%
refetch: a new reply fetches only its own thread, oncePASS100%11%
refetch: deleted replies and a deleted parent rebuild from stored repliesPASS100%8%
refetch: a renamed channel rebuilds every month without fetching any repliesPASS100%8%
raw: every message the history listing returns is stored as Slack returned itPASS100%7%
raw: every thread's replies are stored as Slack returned themPASS100%7%
raw: after changes the store holds Slack's current version of what changedPASS100%6%
retention: under retention, hidden months stay put and a visible reply fetches only its threadPASS100%8%
retention: once retention lifts, a reply in a formerly hidden month fetches only its threadPASS100%6%
interrupted: after a run fails partway, the next runs are complete and a later change fetches only its threadFAIL0%12%
deploy: over a mirror the base wrote, a month's next change fetches only its threadPASS100%11%
page size: history is listed at 999 per page and replies at the largest pagePASS100%5%
preserve: Slack documentsPASS100%0%
preserve: Slack placementPASS100%0%
preserve: incremental changesPASS100%0%
preserve: retentionPASS100%0%
preserve: interrupted runPASS100%0%
preserve: deploy over an existing mirrorPASS100%0%
preserve: channel removalPASS100%0%
preserve: MCP searchPASS100%0%
preserve: MCP read_documentPASS100%0%
preserve: the base's own backend testsPASS100%0%
preserve: backend ruff and mypy --strictPASS100%0%