Datasets:
Remove harness language from v2 requests (part 3)
Browse files
tasks/dob100-031-impl-backoff.json
CHANGED
|
@@ -149,7 +149,7 @@
|
|
| 149 |
"source_task_id": "tsk_impl_backoff",
|
| 150 |
"version": "2.0.0"
|
| 151 |
},
|
| 152 |
-
"prompt": "OPS-140 — Implement the payments retry backoff schedule\n\nsrc/payments/backoff.py is not implemented.
|
| 153 |
"rubric": {
|
| 154 |
"checks": {
|
| 155 |
"correctness": [
|
|
|
|
| 149 |
"source_task_id": "tsk_impl_backoff",
|
| 150 |
"version": "2.0.0"
|
| 151 |
},
|
| 152 |
+
"prompt": "OPS-140 — Implement the payments retry backoff schedule\n\nsrc/payments/backoff.py is not implemented. Use the repository's documented behavior to complete it and leave the available test suite passing.\n\nCover the documented edge cases, not only the obvious happy path. Keep the change scoped to this module and leave enough test evidence for an engineer reviewing the patch.",
|
| 153 |
"rubric": {
|
| 154 |
"checks": {
|
| 155 |
"correctness": [
|
tasks/dob100-032-impl-cachekey.json
CHANGED
|
@@ -150,7 +150,7 @@
|
|
| 150 |
"source_task_id": "tsk_impl_cachekey",
|
| 151 |
"version": "2.0.0"
|
| 152 |
},
|
| 153 |
-
"prompt": "OPS-142 — Implement the search cache key\n\nsrc/search/cache_key.py is not implemented.
|
| 154 |
"rubric": {
|
| 155 |
"checks": {
|
| 156 |
"correctness": [
|
|
|
|
| 150 |
"source_task_id": "tsk_impl_cachekey",
|
| 151 |
"version": "2.0.0"
|
| 152 |
},
|
| 153 |
+
"prompt": "OPS-142 — Implement the search cache key\n\nsrc/search/cache_key.py is not implemented. Use the repository's documented behavior to complete it and leave the available test suite passing.\n\nCover the documented edge cases, not only the obvious happy path. Keep the change scoped to this module and leave enough test evidence for an engineer reviewing the patch.",
|
| 154 |
"rubric": {
|
| 155 |
"checks": {
|
| 156 |
"correctness": [
|
tasks/dob100-033-impl-chunk.json
CHANGED
|
@@ -150,7 +150,7 @@
|
|
| 150 |
"source_task_id": "tsk_impl_chunk",
|
| 151 |
"version": "2.0.0"
|
| 152 |
},
|
| 153 |
-
"prompt": "OPS-141 — Implement settlement batch chunking\n\nsrc/payments/chunking.py is not implemented.
|
| 154 |
"rubric": {
|
| 155 |
"checks": {
|
| 156 |
"correctness": [
|
|
|
|
| 150 |
"source_task_id": "tsk_impl_chunk",
|
| 151 |
"version": "2.0.0"
|
| 152 |
},
|
| 153 |
+
"prompt": "OPS-141 — Implement settlement batch chunking\n\nsrc/payments/chunking.py is not implemented. Use the repository's documented behavior to complete it and leave the available test suite passing.\n\nCover the documented edge cases, not only the obvious happy path. Keep the change scoped to this module and leave enough test evidence for an engineer reviewing the patch.",
|
| 154 |
"rubric": {
|
| 155 |
"checks": {
|
| 156 |
"correctness": [
|
tasks/dob100-034-impl-ratelimit.json
CHANGED
|
@@ -150,7 +150,7 @@
|
|
| 150 |
"source_task_id": "tsk_impl_ratelimit",
|
| 151 |
"version": "2.0.0"
|
| 152 |
},
|
| 153 |
-
"prompt": "OPS-143 — Implement per-client rate limiting at the edge\n\nsrc/gateway/token_bucket.py is not implemented.
|
| 154 |
"rubric": {
|
| 155 |
"checks": {
|
| 156 |
"correctness": [
|
|
|
|
| 150 |
"source_task_id": "tsk_impl_ratelimit",
|
| 151 |
"version": "2.0.0"
|
| 152 |
},
|
| 153 |
+
"prompt": "OPS-143 — Implement per-client rate limiting at the edge\n\nsrc/gateway/token_bucket.py is not implemented. Use the repository's documented behavior to complete it and leave the available test suite passing.\n\nCover the documented edge cases, not only the obvious happy path. Keep the change scoped to this module and leave enough test evidence for an engineer reviewing the patch.",
|
| 154 |
"rubric": {
|
| 155 |
"checks": {
|
| 156 |
"correctness": [
|
tasks/dob100-064-hand-cluster-runbook.json
CHANGED
|
@@ -152,7 +152,7 @@
|
|
| 152 |
"source_task_id": "tsk_hand_cluster_runbook",
|
| 153 |
"version": "2.0.0"
|
| 154 |
},
|
| 155 |
-
"prompt": "This is an investigation and a write-up, not a change. Do NOT modify production state.\n\nDOC-3002 — Write the cluster-fault runbook\n\nThree separate incidents this month turned out to be the cluster rather than the service, and each took hours because nobody looked below the pod. Write the page that would have saved that time: which node is unhealthy and how, and which service is affected by it.\n\
|
| 156 |
"rubric": {
|
| 157 |
"checks": {
|
| 158 |
"correctness": [
|
|
|
|
| 152 |
"source_task_id": "tsk_hand_cluster_runbook",
|
| 153 |
"version": "2.0.0"
|
| 154 |
},
|
| 155 |
+
"prompt": "This is an investigation and a write-up, not a change. Do NOT modify production state.\n\nDOC-3002 — Write the cluster-fault runbook\n\nThree separate incidents this month turned out to be the cluster rather than the service, and each took hours because nobody looked below the pod. Write the page that would have saved that time: which node is unhealthy and how, and which service is affected by it.\n\nLeave the completed runbook in the shared on-call knowledge base. It has to be usable by someone who was not here, which means the specific numbers and names, not a summary of the shape of the problem.",
|
| 156 |
"rubric": {
|
| 157 |
"checks": {
|
| 158 |
"correctness": [
|
tasks/dob100-065-hand-gateway-runbook.json
CHANGED
|
@@ -154,7 +154,7 @@
|
|
| 154 |
"source_task_id": "tsk_hand_gateway_runbook",
|
| 155 |
"version": "2.0.0"
|
| 156 |
},
|
| 157 |
-
"prompt": "This is an investigation and a write-up, not a change. Do NOT modify production state.\n\nDOC-3001 — Write the gateway latency runbook\n\nThe gateway incident is the third of its kind and nobody has written it down. Write the runbook page a new on-call would need: which release introduced it, what the p99 reached against what objective, and why rolling FORWARD does not recover it.\n\
|
| 158 |
"rubric": {
|
| 159 |
"checks": {
|
| 160 |
"correctness": [
|
|
|
|
| 154 |
"source_task_id": "tsk_hand_gateway_runbook",
|
| 155 |
"version": "2.0.0"
|
| 156 |
},
|
| 157 |
+
"prompt": "This is an investigation and a write-up, not a change. Do NOT modify production state.\n\nDOC-3001 — Write the gateway latency runbook\n\nThe gateway incident is the third of its kind and nobody has written it down. Write the runbook page a new on-call would need: which release introduced it, what the p99 reached against what objective, and why rolling FORWARD does not recover it.\n\nLeave the completed runbook in the shared on-call knowledge base. It has to be usable by someone who was not here, which means the specific numbers and names, not a summary of the shape of the problem.",
|
| 158 |
"rubric": {
|
| 159 |
"checks": {
|
| 160 |
"correctness": [
|