blakeslee-research/nucleic-purpose-classifier
3
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

updating purpose-classifier data:

Browse Source
This commit is contained in:
abkslm
2026-08-02 20:15:13 -07:00
parent 98311aa932
commit 0f639bfa05
21 changed files with 14248 additions and 14463 deletions
Download Patch File Download Diff File Expand all files Collapse all files
data/round2-09.jsonl
+200 -200
View File
@@ -1,200 +1,200 @@
{"prompt": "the exam thing", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.55, "slice": "vague-eval", "lang": "en"}
{"prompt": "our staging kafka has one partition and prod has twelve, which is why ordering bugs never show up first", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.3, "slice": "boundary", "lang": "en"}
{"prompt": "attempt state machine is spread across four files as boolean columns and ad-hoc checks:\n\nattempt.startedAt // set on create\nattempt.submittedAt // set on submit, also set by the nightly auto-submit job\nattempt.gradedAt // set by the grading worker\nattempt.voidedAt // set by support scripts only\nattempt.mergedIntoId // set by the merge script, and the old attempt keeps its submittedAt\n\nchecks like `if (attempt.submittedAt && !attempt.gradedAt)` appear in eleven places, three of which forget voidedAt, and the review screen's definition of \"latest attempt\" is different again", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "pasted-context", "lang": "en"}
{"prompt": "one grading calculation, three call sites", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.55, "slice": "core", "lang": "en"}
{"prompt": "our exam load is 40,000 concurrent students for two hours twice a year and idle the rest of the time", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.75, "slice": "boundary", "lang": "en"}
{"prompt": "the WMS has two definitions of \"aisle available\" — the dispatcher's, which asks whether any robot could enter, and the console's, which asks whether a human could — and during maintenance they disagree in the dangerous direction. reconcile them into one predicate with an explicit meaning, keep the console's display identical for the normal case, and tell me which existing callers change behaviour", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "core", "lang": "en"}
{"prompt": "quiz submissions vanish for a handful of students each exam and this is all we get:\n\nPrismaClientKnownRequestError:\nInvalid `prisma.submission.create()` invocation:\n\nUnique constraint failed on the fields: (`attemptId`,`questionId`)\n at RequestHandler.handleRequestError (/app/node_modules/@prisma/client/runtime/library.js:121:6412)\n at async POST (/app/app/api/attempts/[id]/answers/route.ts:41:22)\n\n attemptId: 'atmp_01HR9K2M'\n questionId: 'q_88412'\n studentId: 'usr_4471'\n retryCount: 2\n clientTimestamp: 2026-07-29T11:02:14.881Z\n serverTimestamp: 2026-07-29T11:02:19.114Z\n\nthe client retries on a slow response, and the student sees their answer disappear from the review screen afterwards", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.75, "slice": "pasted-context", "lang": "en"}
{"prompt": "detection rules stopped firing overnight and the pipeline claims everything is healthy:\n\n[ingest] 2026-07-29T02:00:04Z bulk index 8,412 docs into logs-edr-2026.07.29 took 412ms\n[ingest] 2026-07-29T02:00:09Z bulk index 8,118 docs took 388ms\n[rules] 2026-07-29T02:01:00Z executing 141 rules over window [01:56:00, 02:01:00]\n[rules] 2026-07-29T02:01:04Z 0 alerts generated (previous run: 22)\n[rules] 2026-07-29T02:06:00Z executing 141 rules over window [02:01:00, 02:06:00]\n[rules] 2026-07-29T02:06:03Z 0 alerts generated\n[ingest] 2026-07-29T02:07:11Z index logs-edr-2026.07.30 created\n\nthe index for tomorrow's date appearing at 02:07 is the only odd thing i can see, and our rules query `logs-edr-*` with a `@timestamp` range", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.8, "slice": "pasted-context", "lang": "en"}
{"prompt": "robot cards should sort problems first", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.3, "slice": "boundary", "lang": "en"}
{"prompt": "what counts as the latest attempt?", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "core", "lang": "en"}
{"prompt": "a district's procurement requires WCAG 2.2 AA conformance, per-student time extensions and a VPAT within six weeks, and we have none of those. i want the realistic plan: what we can genuinely fix, what we have to declare as a gap with a remediation date, and how we word a VPAT that is honest without losing the contract", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.85, "slice": "core", "lang": "en"}
{"prompt": "one enrichment provider interface", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "core", "lang": "en"}
{"prompt": "attempt state as an enum, not five columns", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "core", "lang": "en"}
{"prompt": "task API is what the robot firmware integrates against, documented in a wiki page from 2023:\n\nGET /v1/tasks/next?robot_id=&capabilities=\n long-polls for up to 30 seconds; returns 204 when nothing is available\n a returned task is leased for 90 seconds and must be acked or it returns to the queue\nPOST /v1/tasks/{id}/ack { robot_id, accepted: bool, reason? }\nPOST /v1/tasks/{id}/progress { robot_id, node, percent }\nPOST /v1/tasks/{id}/complete { robot_id, outcome: \"done\"|\"failed\"|\"aborted\", detail? }\n completing a task that has already been requeued returns 409 and the robot must stop\n progress after the lease expires is accepted but ignored, which firmware treats as success\n\nwrite the integration reference; the lease semantics and the ignored-progress behaviour are what firmware keeps getting wrong", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "pasted-context", "lang": "en"}
{"prompt": "three places compute a student's grade and they disagree in the third decimal:\n\n// app/lib/grades.ts — student view\nconst grade = assessments.reduce((sum, a) =>\n sum + Math.round(scoreFor(a) * 10) / 10 * a.weight, 0)\n\n// GradeService.java — teacher view\ntotal = total.add(s.getScore().multiply(a.getWeight())); // BigDecimal, rounded once at the end\n\n-- exports/grades.sql\nSELECT round(sum(s.score * a.weight)::numeric, 1) FROM ...\n\nthe teacher view is the one the institution treats as authoritative, and all three are visible to different users on the same day", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "pasted-context", "lang": "en"}
{"prompt": "rule engine has three ways to express the same condition and analysts use all of them:\n\n# style 1 — lucene string\nquery: 'event.code:5145 and winlog.event_data.ShareName:\"\\\\\\\\*\\\\IPC$\"'\n\n# style 2 — elasticsearch DSL, raw\nquery_dsl: { bool: { filter: [ { term: { \"event.code\": \"5145\" } } ] } }\n\n# style 3 — our own yaml shorthand, added last year\nmatch:\n event.code: 5145\n winlog.event_data.ShareName: \"*IPC$\"\n\nall three go through different code paths, only style 3 validates field names, and style 2 lets an analyst write a query that scans every index we have", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.65, "slice": "pasted-context", "lang": "en"}
{"prompt": "is our tenant filter applied everywhere?", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "boundary", "lang": "en"}
{"prompt": "exam week is three weeks away, lost answers are our most damaging bug, and the attempt model has assumptions in it that stopped being true when students started using two devices. i'd like the plan for what we change before exams and what we deliberately leave until after, with the risk of each decision written down so nobody relitigates it at midnight during the exam support has forty tickets from last term's exams if you want the failure patterns.", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.85, "slice": "core", "lang": "en"}
{"prompt": "we need a position on how the LMS syncs with student information systems, given opaque ids that change each academic year and a district that rate limits us to ten requests a second. design it, then implement the resumable sync loop so we can test against their sandbox their sandbox is available and their ids change every august, which is the awkward part.", "purpose": "planning", "secondary": "backendImpl", "mixed": true, "difficulty": 0.8, "slice": "mixed", "lang": "en"}
{"prompt": "detection rule for lateral movement, which the security team says has too many false positives:\n\nname: Suspicious SMB session enumeration\nindex: logs-edr-*\nquery: |\n event.code:5145 and winlog.event_data.ShareName:\"\\\\\\\\*\\\\IPC$\"\n and winlog.event_data.RelativeTargetName:(\"srvsvc\" or \"wkssvc\" or \"samr\")\ninterval: 5m\nwindow: 5m\nthreshold:\n field: source.ip\n value: 10\nseverity: high\nsuppression: none\n\nfires about 40 times a day, almost always from the same six management servers, and nobody has tuned it since it was imported from a blog post", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.65, "slice": "pasted-context", "lang": "en"}
{"prompt": "robot one, again", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "vague-eval", "lang": "en"}
{"prompt": "a student's grade is computed three times in three languages and the three disagree in the third decimal, with the teacher's view treated as authoritative by the institution. consolidate onto that behaviour, keep the exports byte-identical where they already agree, and list every student whose displayed grade will change as a result the institution treats the teacher's view as authoritative and will not accept a change to it.", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "core", "lang": "en"}
{"prompt": "quiz player has to survive exam conditions, which means an autosave state that never lies, a keyboard-operable navigator, a timer that doesn't shout every second, and a graceful fallback when javascript dies mid-exam. build it to the spec, and tell me which of those the current player gets wrong today forty thousand students sit exams in the same two-hour window twice a year.", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.8, "slice": "core", "lang": "en"}
{"prompt": "what does a bulk index rejection actually do to the events in that batch — are they lost or retried", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "core", "lang": "en"}
{"prompt": "inventory counts drift from reality by a few units a day and reconciliation can't explain it:\n\ntask 88401 PICK sku=SKU-4471 qty=3 from=A7-03-02 robot=R-041 status=COMPLETED at=11:02:14\ntask 88402 PICK sku=SKU-4471 qty=2 from=A7-03-02 robot=R-018 status=COMPLETED at=11:02:16\ninventory event sku=SKU-4471 location=A7-03-02 delta=-3 source=task-88401 at=11:02:19\ninventory event sku=SKU-4471 location=A7-03-02 delta=-2 source=task-88402 at=11:02:19\ncycle count sku=SKU-4471 location=A7-03-02 counted=4 system=2 at=18:00:00\n\nboth picks were dispatched from a snapshot showing 5 units, and the location physically held 5", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.8, "slice": "pasted-context", "lang": "en"}
{"prompt": "robots collide at aisle intersections about once a week and the traffic manager logs look reasonable:\n\n11:02:14.101 [traffic] R-041 requests reservation for node N-A7-INT (aisle A7 intersection)\n11:02:14.104 [traffic] reservation granted to R-041, expires 11:02:44\n11:02:14.112 [traffic] R-018 requests reservation for node N-A7-INT\n11:02:14.115 [traffic] reservation denied, held by R-041\n11:02:14.118 [traffic] R-018 enters waiting state\n11:02:29.881 [traffic] R-041 heartbeat missed (last 11:02:14.104)\n11:02:29.884 [traffic] reservation for N-A7-INT released (holder unresponsive)\n11:02:29.887 [traffic] reservation granted to R-018\n11:02:31.114 [traffic] R-041 heartbeat resumed, continues along reserved path\n\nR-041 kept moving through the intersection during those fifteen seconds", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.85, "slice": "pasted-context", "lang": "en"}
{"prompt": "elasticsearch rejects writes during our morning peak and the cluster looks healthy otherwise:\n\n{\n \"error\": {\n \"type\": \"es_rejected_execution_exception\",\n \"reason\": \"rejected execution of coordinating operation [coordinating_and_primary_bytes=0, replica_bytes=0, all_bytes=0, coordinating_operation_bytes=104857600, max_coordinating_and_primary_bytes=104857600]\"\n },\n \"status\": 429\n}\n\nnode stats:\n indexing.index_current: 412\n thread_pool.write.queue: 200 (capacity 200)\n thread_pool.write.rejected: 41,882\n jvm.mem.heap_used_percent: 71\n indices.indexing.index_time_in_millis rate: 88ms/doc\n\nwe bulk index in 50MB batches from four ingest workers", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.75, "slice": "pasted-context", "lang": "en"}
{"prompt": "reservation logic in the traffic manager, which decides whether robots can enter a node:\n\npublic boolean tryReserve(String nodeId, String robotId, Duration ttl) {\n Reservation existing = reservations.get(nodeId);\n if (existing != null && !existing.isExpired(clock.instant())) {\n return false;\n }\n reservations.put(nodeId, new Reservation(robotId, clock.instant().plus(ttl)));\n return true;\n}\n\npublic void heartbeat(String robotId) {\n lastSeen.put(robotId, clock.instant());\n}\n\n// separate thread, every second\nreservations.entrySet().removeIf(e ->\n Duration.between(lastSeen.getOrDefault(e.getValue().robotId(), Instant.EPOCH), clock.instant()).getSeconds() > 15);\n\nis releasing a reservation on a missed heartbeat sound, given a robot that's still physically moving?", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.85, "slice": "pasted-context", "lang": "en"}
{"prompt": "design doc for our attempt model, written before the exam pilot. does it survive contact with 40,000 students?\n\n## Attempts\nAn attempt is created when a student opens a quiz and holds every answer as a row. Answers are upserted as the student progresses, so a lost connection loses nothing. An attempt is submitted once; submission is idempotent.\n\n## Assumptions\n- A student has one attempt open at a time.\n- Answers are small and can be written on every keystroke pause.\n- The client is authoritative for question order.\n\n## Not covered\nProctoring. Offline attempts. Two devices on the same attempt.\n\nstudents routinely open a quiz on a laptop and a phone, and \"upserted\" is a create in the code", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.75, "slice": "pasted-context", "lang": "en"}
{"prompt": "kafka consumer config for the robot fleet, which rebalances constantly:\n\nmax.poll.records: 500\nmax.poll.interval.ms: 300000\nsession.timeout.ms: 10000\nheartbeat.interval.ms: 3000\nenable.auto.commit: true\nauto.commit.interval.ms: 5000\nfetch.min.bytes: 1\ngroup.instance.id: (unset)\n\ntwelve robots, each a consumer in the same group, each processing a task for up to 90 seconds; robots go offline briefly when they pass through the racking in aisle A7", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.75, "slice": "pasted-context", "lang": "en"}
{"prompt": "npm audit before the exam period freeze, what goes in:\n\nnext 14.2.0 - 14.2.29\nSevere: Server-Side Request Forgery in Next.js image optimisation\nfix available via `npm audit fix --force`\nWill install [email protected], which is a breaking change\n\n@prisma/client 5.14.0 - 5.19.1\nModerate: Prisma Client leaks connection strings in error messages\nfix available via `npm audit fix`\n\nsharp 0.32.0 - 0.33.4\nHigh: Denial of service via crafted image\nfix available via `npm audit fix`\n\n4 vulnerabilities (1 moderate, 2 high, 1 severe)\n\nwe are three weeks from exam week and the next major is a two-day migration", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.4, "slice": "pasted-context", "lang": "en"}
{"prompt": "enrichment providers each handle failure differently, which is why one slow provider stalls everything:\n\n# asn.py\nresp = requests.get(url) # no timeout at all\nreturn resp.json()[\"asn\"]\n\n# geo.py\ntry:\n resp = requests.get(url, timeout=2)\nexcept requests.Timeout:\n return None # silently unenriched\n\n# threatintel.py\nfor attempt in range(5):\n try: return requests.get(url, timeout=10).json()\n except Exception: time.sleep(attempt) # up to 10 seconds of sleeping in the pipeline\n\n# internal_assets.py\nreturn self.cache[ip] # KeyError propagates and kills the batch", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.65, "slice": "pasted-context", "lang": "en"}
{"prompt": "accessibility requirement from a district's procurement, which we have to answer honestly:\n\n\"The platform shall conform to WCAG 2.2 AA. All assessment activities shall be completable using a keyboard alone and with a screen reader. Time limits shall be adjustable or extendable by an instructor for individual students. Content shall not rely on colour alone to convey meaning. The supplier shall provide a current VPAT and a remediation plan for any non-conformance.\"\n\nour quiz navigation is mouse-only in two places, time limits are per-assessment with no per-student override, and we have never produced a VPAT. i want the plan, the honest gaps, and what we can claim by the deadline in six weeks", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.85, "slice": "pasted-context", "lang": "en"}
{"prompt": "bulk batches down to 5MB", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.3, "slice": "boundary", "lang": "en"}
{"prompt": "alert list should support j and k", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.35, "slice": "core", "lang": "en"}
{"prompt": "triage view needs a dark theme default", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.3, "slice": "boundary", "lang": "en"}
{"prompt": "why does the group rebalance so often?", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.65, "slice": "boundary", "lang": "en"}
{"prompt": "aisle screen", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "vague-eval", "lang": "en"}
{"prompt": "teachers are dealing with duplicate attempts, an auto-submit job they don't know about and a review screen that shows only the latest attempt, and every one of those has generated support tickets this term. write the page that explains attempts as they actually work, in language a teacher will read the week before exams rather than during them the page should be readable in five minutes by someone who has never filed a support ticket.", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "core", "lang": "en"}
{"prompt": "warehouse runbook still describes the conveyor system that was removed two years ago, and the robot procedures live in the shift supervisors' heads. write the runbook for the robot fleet, ordered by what someone woken at three in the morning needs first, and be explicit about which actions are never safe during operations the supervisors printing this will have it laminated, so keep it short and ordered.", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "boundary", "lang": "en"}
{"prompt": "an auditor has asked six questions about telemetry collection, retention, tenant isolation, alert deletion, rule versioning and orphaned alerts, and at least three of our honest answers are unflattering. write the controls document from the code, marking what we can't substantiate rather than smoothing over it our compliance lead reads it first and would rather see a gap than a confident half-truth.", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "boundary", "lang": "en"}
{"prompt": "nobody can tell me whether a robot that loses wifi mid-aisle can have its reservation given away while it is still moving, or whether some other interlock saves us. read the traffic manager, the heartbeat handling and the sweep together, and tell me exactly what sequence of events produces the situation we saw in May", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.9, "slice": "core", "lang": "en"}
{"prompt": "i'd like an honest read of whether our tenant isolation can be bypassed by a crafted rule, given that rules can specify their own index pattern, and the fix if it can", "purpose": "review", "secondary": "backendImpl", "mixed": true, "difficulty": 0.8, "slice": "mixed", "lang": "en"}
{"prompt": "instructor dashboard times out for two institutions that are up for renewal, and i want the diagnosis before the rewrite. work out where the time actually goes, then restructure the query so it returns in under a second at their size both institutions are up for renewal, so a number i can quote would help.", "purpose": "debugging", "secondary": "backendImpl", "mixed": true, "difficulty": 0.75, "slice": "mixed", "lang": "en"}
{"prompt": "rule versioning needs designing and starting in the same quarter. give me the model — immutable versions, alert references, what deletion means — then build the versions table and the write path so new alerts start carrying a version immediately", "purpose": "planning", "secondary": "backendImpl", "mixed": true, "difficulty": 0.8, "slice": "mixed", "lang": "en"}
{"prompt": "task API reference has to exist for the firmware team, and while writing it i'd like confirmation that late progress reports really are accepted and ignored, because the firmware treats that as success", "purpose": "writing", "secondary": "review", "mixed": true, "difficulty": 0.6, "slice": "mixed", "lang": "en"}
{"prompt": "three prisma query styles for a teacher's courses disagree about archived courses and one bypasses row-level security entirely. unify them, and tell me whether that raw query has been leaking other teachers' courses this whole time", "purpose": "refactor", "secondary": "review", "mixed": true, "difficulty": 0.7, "slice": "mixed", "lang": "en"}
{"prompt": "is the grading recalculation safe to run concurrently for the same enrolment, or are we relying on luck", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "core", "lang": "en"}
{"prompt": "exam timer keeps counting while the browser tab is backgrounded on ios, which it shouldn't", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.35, "slice": "core", "lang": "en"}
{"prompt": "we need a plan for running two warehouse sites from one WMS instance without them affecting each other", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.8, "slice": "boundary", "lang": "en"}
{"prompt": "the aisle drain command should refuse while robots are inside and report which ones are blocking, rather than draining tasks and leaving the robots stranded mid-aisle as it does today. it also needs to be safe to call repeatedly from the console by a supervisor who is watching the screen rather than reading the response", "purpose": "backendImpl", "secondary": null, "mixed": false, "difficulty": 0.65, "slice": "boundary", "lang": "en"}
{"prompt": "our ingestion, enrichment and rules services each define their own dataclasses for the same event schema, which is why a field rename last month silently dropped enrichment for one event type. give them one shared schema definition with versioning, and confirm from a day of production events that nothing is parsed differently afterwards a field rename last month silently dropped enrichment for one event type and nobody noticed for a week.", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "boundary", "lang": "en"}
{"prompt": "attempt design doc claims answers are upserted and submission is idempotent, and neither is true in the code as far as i can tell. go through the doc claim by claim against the current implementation and tell me which parts are aspirational, because exam week is close and i need to know what we actually have exam week is close enough that i need to know what we actually have rather than what we meant.", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.75, "slice": "boundary", "lang": "en"}
{"prompt": "one query style for detection rules", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "boundary", "lang": "en"}
{"prompt": "our three LMS components each implement optimistic updates with a different rollback strategy, and the quiz one rolls back to a value that may already be stale. unify them behind one approach, and while you're in there tell me whether the quiz rollback has ever silently discarded a saved answer", "purpose": "refactor", "secondary": "review", "mixed": true, "difficulty": 0.65, "slice": "mixed", "lang": "en"}
{"prompt": "the course cache is a module-level Map with no eviction and it is most of our memory growth in production. put a bound and a TTL on it, then confirm from the request pattern whether caching there is worth keeping at all", "purpose": "refactor", "secondary": "review", "mixed": true, "difficulty": 0.55, "slice": "mixed", "lang": "en"}
{"prompt": "quiz navigator and the drag-to-order questions both fail the accessibility audit and both need keyboard alternatives. fix them, and write the VPAT section covering assessment activities", "purpose": "frontendImpl", "secondary": "writing", "mixed": true, "difficulty": 0.7, "slice": "mixed", "lang": "en"}
{"prompt": "detection rules are written in three different syntaxes because we added a friendlier one without removing the others, and only the newest validates field names. before consolidating i want a view on whether we can migrate existing rules automatically, what we'd break for analysts who write raw DSL, and whether the friendlier syntax is expressive enough for the rules that matter", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.8, "slice": "boundary", "lang": "en"}
{"prompt": "robot firmware team integrates against our task API from a wiki page written in 2023, and the two things they consistently get wrong are lease expiry and the fact that late progress reports are accepted but ignored. write the reference documentation with those two impossible to misread, including what a robot should do when it gets a 409 the firmware release cycle is six weeks, so anything ambiguous costs us a quarter.", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "core", "lang": "en"}
{"prompt": "what guarantees does our nightly sync make when the district's API returns a partial page", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.65, "slice": "boundary", "lang": "en"}
{"prompt": "a walkthrough of how a pick becomes an inventory movement would help before i touch reconciliation", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "boundary", "lang": "en"}
{"prompt": "one aisle stops receiving tasks", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.75, "slice": "core", "lang": "en"}
{"prompt": "attempt lifecycle is five nullable timestamp columns and eleven ad-hoc checks, three of which forget the voided case entirely. model it as an explicit state machine, migrate the existing rows including the merged ones, and keep every current query returning the same rows it does today the merged attempts from the support scripts are the awkward rows, and there are about two hundred.", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.75, "slice": "boundary", "lang": "en"}
{"prompt": "pick tasks stop flowing to one aisle every few days, kafka side looks fine to me:\n\n2026-07-29T11:02:14Z INFO [task-dispatcher] assigning task 88412 to robot R-041 aisle=A7\n2026-07-29T11:02:14Z INFO [task-dispatcher] produced to topic wms.tasks partition=3 offset=41882104\n2026-07-29T11:02:44Z WARN [task-dispatcher] no ack from R-041 after 30s, task 88412 requeued\n2026-07-29T11:03:14Z WARN [task-dispatcher] no ack from R-041 after 30s, task 88412 requeued\n2026-07-29T11:03:44Z ERROR [task-dispatcher] task 88412 exceeded requeue limit, dead-lettered\n2026-07-29T11:03:45Z INFO [consumer-group wms-robots] rebalance triggered, 12 members\n2026-07-29T11:03:52Z INFO [consumer-group wms-robots] rebalance complete, R-041 assigned partitions [3]\n\nrebalances happen every few minutes and R-041's logs show it never received the task at all", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.8, "slice": "pasted-context", "lang": "en"}
{"prompt": "course player buffers on video for one school district and nobody else:\n\nnetwork tab, same lesson, two sites:\n district A: GET /media/lesson-4471/hls/720p/seg_00041.ts 200 1.2MB ttfb 2,841ms total 8,112ms\n district B: GET /media/lesson-4471/hls/720p/seg_00041.ts 200 1.2MB ttfb 88ms total 214ms\n\nresponse headers (district A):\n x-cache: MISS\n age: 0\n cf-ray: 8f2b1c40-ORD\n vary: Origin, Accept-Encoding, Cookie\n\ndistrict A's proxy adds a `Cookie` header to every media request, district B's doesn't", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "pasted-context", "lang": "en"}
{"prompt": "SIEM's enrichment lookups time out under load and the queue backs up:\n\npy-spy dump --pid 41221:\nThread 0x7f1a (active): \"MainThread\"\n _wait_for_tstate_lock (threading.py:1116)\n join (threading.py:1096)\n enrich_batch (enrichment/pipeline.py:141)\n process (enrichment/pipeline.py:88)\nThread 0x7f2b (idle): \"enrich-0\"\n read (socket.py:718)\n _read_status (http/client.py:280)\n getresponse (http/client.py:1428)\n lookup_asn (enrichment/providers/asn.py:41)\n\n... 63 more idle threads, all in lookup_asn\n\nthe ASN provider has no timeout set on its session, and we spawn one thread per event in a batch of 500", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "pasted-context", "lang": "en"}
{"prompt": "las notas calculadas no coinciden con las que ven los profesores, aquí un caso:\n\nalumno 4471, curso \"Álgebra II\"\n tarea 1 nota 8,5 peso 20%\n tarea 2 nota 7,0 peso 20%\n examen nota 6,5 peso 60%\n\ncálculo esperado: 8,5*0,2 + 7,0*0,2 + 6,5*0,6 = 7,00\ncálculo mostrado en el panel del profesor: 7,00\ncálculo mostrado al alumno: 7,33\ncálculo en el export CSV: 7,0\n\nel panel del alumno redondea antes de ponderar, y el export usa una consulta distinta escrita hace dos años", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.65, "slice": "pasted-context", "lang": "es"}
{"prompt": "next.js app leaks memory in production and the pod restarts every few hours:\n\nheap snapshot comparison (30 min apart):\n (array) +412 MB +1,204,118 objects\n Prisma.QueryEngine +188 MB\n (closure) +141 MB +882,441 objects\n Response +88 MB\n Map +41 MB\n\nretainers for the largest (array):\n global → cacheMap → Map → entries → Array\n app/lib/courseCache.ts:22\n\ncourseCache is a module-level Map keyed by course id, populated on every request, never evicted, and the server runs in a long-lived node process", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "pasted-context", "lang": "en"}
{"prompt": "grading service's concurrency, which i'd like a second opinion on before we scale it up:\n\n@Transactional\npublic Grade recalculate(Long enrolmentId) {\n Enrolment e = enrolments.findById(enrolmentId).orElseThrow();\n List<Submission> subs = submissions.findByEnrolment(e.getId());\n BigDecimal total = BigDecimal.ZERO;\n for (Assessment a : e.getCourse().getAssessments()) {\n Submission s = subs.stream().filter(x -> x.getAssessmentId().equals(a.getId()))\n .max(comparing(Submission::getAttempt)).orElse(null);\n if (s == null) continue;\n total = total.add(s.getScore().multiply(a.getWeight()));\n }\n e.setGrade(total.setScale(2, RoundingMode.HALF_UP));\n return grades.save(new Grade(e, total));\n}\n\nthis runs on submission, on assessment weight changes, and nightly for every enrolment in the institution", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "pasted-context", "lang": "en"}
{"prompt": "bitte einmal drüberschauen, bevor das in die Prüfungsphase geht:\n\nexport async function POST(req: Request, { params }: { params: { id: string } }) {\n const body = await req.json()\n const attempt = await prisma.attempt.findUnique({ where: { id: params.id } })\n if (!attempt) return new Response(\"not found\", { status: 404 })\n if (attempt.submittedAt) return new Response(\"already submitted\", { status: 409 })\n await prisma.answer.create({\n data: { attemptId: attempt.id, questionId: body.questionId, value: body.value },\n })\n return Response.json({ ok: true })\n}\n\nder Client sendet bei langsamer Verbindung erneut, und es gibt keinen Idempotenzschlüssel; in der Prüfungswoche sind das 40.000 gleichzeitige Versuche", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "pasted-context", "lang": "de"}
{"prompt": "ingestion pipeline's batching, which i suspect is why elasticsearch rejects us:\n\ndef run(self):\n batch = []\n for event in self.source:\n batch.append(self.transform(event))\n if len(batch) >= self.batch_size: # batch_size = 10_000\n self.es.bulk(body=batch, request_timeout=120)\n batch = []\n if batch:\n self.es.bulk(body=batch, request_timeout=120)\n\nfour workers run this, batch_size is 10,000 documents which averages 50MB, there's no retry on 429, and a rejected bulk loses the whole batch silently because we don't check the per-item response", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.75, "slice": "pasted-context", "lang": "en"}
{"prompt": "query behind the instructor dashboard, which times out for our largest institution:\n\nSELECT c.id, c.title, count(distinct e.student_id) AS students,\n avg(g.value) FILTER (WHERE g.value IS NOT NULL) AS avg_grade,\n count(*) FILTER (WHERE s.submitted_at IS NULL AND a.due_at < now()) AS overdue,\n (SELECT count(*) FROM messages m WHERE m.course_id = c.id AND m.read_at IS NULL) AS unread\nFROM courses c\nJOIN enrolments e ON e.course_id = c.id\nLEFT JOIN grades g ON g.enrolment_id = e.id\nLEFT JOIN assessments a ON a.course_id = c.id\nLEFT JOIN submissions s ON s.assessment_id = a.id AND s.student_id = e.student_id\nWHERE c.institution_id = $1 AND c.archived_at IS NULL\nGROUP BY c.id, c.title;\n\n1,200 courses, 88,000 enrolments, 4.1M submissions for that institution", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.75, "slice": "pasted-context", "lang": "en"}
{"prompt": "support's notes on the exam-week incidents, they need to become a page teachers can read:\n\n- students on flaky wifi sometimes see \"answer not saved\" and refresh, which creates a second attempt\n- teachers then see two attempts and don't know which is authoritative — it's the one with the later submittedAt\n- an attempt with no submittedAt after the exam window closes is auto-submitted by a nightly job, which teachers don't know exists\n- the review screen shows answers from the latest attempt only, which is why students say answers \"disappeared\"\n- teachers can merge attempts through a support ticket, which takes a day and a database script\n- none of this is in any documentation, and exam week is in three weeks\n\nwrite the page for teachers, and separately tell me which of these are documentation problems and which are product problems", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "pasted-context", "lang": "en"}
{"prompt": "notes from the security team's rule review, i need to turn them into a rule-writing guide for analysts:\n\n- every rule needs an owner, a rationale and an expected volume, and today most have none\n- rules imported from blog posts are the biggest source of noise; the SMB one fires 40 times a day\n- suppression by source.ip for known management hosts should be the default, not an afterthought\n- thresholds are absolute counts, so a rule tuned for one customer's volume is wrong for another\n- rules query `logs-*` by habit, which now includes tomorrow's index and non-EDR data\n- there's no test procedure; analysts write a rule and see if it fires in production\n- a rule that generates zero alerts for a week should be reviewed, not left running\n\nwrite the guide, aimed at analysts who write rules but don't operate the platform", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "pasted-context", "lang": "en"}
{"prompt": "o resumo do incidente de ontem, para as escolas afetadas:\n\n09:12 professores relatam que as notas mostradas aos alunos não coincidem com o painel\n09:40 confirmamos: o painel do aluno arredonda antes de ponderar\n10:05 verificamos que o export CSV usa uma consulta diferente, escrita há dois anos\n10:30 três cálculos distintos identificados para a mesma nota\n11:15 decidimos que o painel do professor é a fonte de verdade\n12:00 correção aplicada aos outros dois; nenhuma nota gravada estava errada\n\nnenhum aluno foi avaliado incorretamente, mas alguns viram um valor diferente durante cerca de três horas; as escolas querem saber se as notas finais foram afetadas", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "pasted-context", "lang": "pt"}
{"prompt": "WMS operator's manual covers the old conveyor system and nothing about the robots. what's true now:\n\n- tasks are dispatched from the WMS to a robot fleet over kafka, with a 90 second lease\n- a robot that loses connectivity keeps executing its current task and reports on reconnect\n- the traffic manager grants node reservations; a robot without a reservation stops and waits\n- an aisle can be put into maintenance mode from the console, which drains tasks but does not recall robots already inside\n- cycle counts run nightly and discrepancies over 2 units page the shift supervisor\n- there is a physical e-stop per aisle that the software cannot override, and a software pause that it can\n- recovering a stuck robot means driving it manually from the console, which requires a role most supervisors don't have\n\nwrite the operator's manual section for the robot fleet", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "pasted-context", "lang": "en"}
{"prompt": "changelog for the LMS release, from the commits since 6.3:\n\n41c9e0b fix(attempts): answers are upserted rather than created, fixing lost answers on retry\n88f21c0 feat(grading): one grading path for the student view, teacher view and export\nc0aa774 fix(media): media requests no longer vary on Cookie, restoring CDN caching\n2e91b45 feat(exams): attempts can be merged from the teacher's screen\naa30f19 perf(dashboard): instructor dashboard query rewritten, 8s to 400ms\n9c1d004 chore: minimum node version is now 22\n4410bb7 fix(a11y): quiz navigation is keyboard operable\nb77e910 feat(api): institution-scoped API tokens\n\nour readers are school IT administrators; two of these change behaviour they'll notice and one needs action from them", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.45, "slice": "pasted-context", "lang": "en"}
{"prompt": "auditor's questions about our SIEM deployment, which we've never had to answer in writing:\n\n1. What data is collected from endpoints, and can a customer see the full list?\n2. How long is raw telemetry retained, and where?\n3. Who can read another tenant's alerts, and how is that prevented?\n4. Can an analyst delete an alert, and is that recorded?\n5. How are detection rules versioned, and can you show which rule version produced a given alert?\n6. What happens to alerts when a rule is deleted?\n\nour rules live in a git repo but alerts store only the rule name; deleting a rule leaves orphaned alerts; and tenant isolation is a filter applied in the query layer\n\nwrite the controls document, marking clearly what we cannot currently substantiate", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "pasted-context", "lang": "en"}
{"prompt": "我们的告警规则文档只有一个示例，运维和分析师都在猜。目前规则引擎的实际行为如下：\n\n- 规则每 5 分钟执行一次，查询窗口默认也是 5 分钟，两者不一致时以窗口为准\n- 窗口是左闭右开，边界上的事件会在两个窗口中被计算一次还是零次，取决于 `@timestamp` 的精度\n- 阈值是绝对值，不随数据量缩放；同一条规则在不同租户下的表现完全不同\n- 抑制（suppression）只按字段去重,不做时间衰减，抑制窗口固定 1 小时且不可配置\n- 规则被删除后，已产生的告警仍然保留，但无法回溯到规则内容\n- 规则里写 `index: logs-*` 会匹配到未来日期的索引，这在跨时区部署里会导致漏报\n\n请写成给分析师看的规则编写文档，把窗口边界和抑制这两点讲清楚\n\n目前规则文件长这样，文档里也只有这一个例子：\n\nname: Suspicious SMB session enumeration\nindex: logs-edr-*\ninterval: 5m\nwindow: 5m\nquery: |\n event.code:5145 and winlog.event_data.ShareName:\"\\\\\\\\*\\\\IPC$\"\nthreshold:\n field: source.ip\n value: 10\nsuppression:\n by: [source.ip]\n window: 1h # 实际上这个字段被忽略，永远是 1 小时\nseverity: high\nowner: (empty)\n\n另外，规则删除后 alerts 表里的 rule_name 还在，但 rule body 无法追溯", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.65, "slice": "pasted-context", "lang": "zh"}
{"prompt": "on-call runbook for the warehouse is a laminated sheet from the conveyor era. what the team does now:\n\n- \"aisle stopped\" is the most common page; first check whether it's an e-stop (physical) or a software pause\n- if the traffic manager is granting reservations but robots aren't moving, restart the dispatcher, not the traffic manager\n- restarting the traffic manager during operations releases every reservation at once, which is how we had the near-miss in May\n- a robot that missed its heartbeat but is still moving is the dangerous case; the only safe action is the aisle e-stop\n- kafka consumer lag above 500 on wms.tasks means the dispatcher is behind and picks will be late, not lost\n- never drain an aisle that has robots inside it; drain, then wait for the aisle to report empty\n\nwrite the runbook, ordered by what a supervisor at 3am would need first", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "pasted-context", "lang": "en"}
{"prompt": "eslint and tsc on the LMS app, the gate goes on next sprint:\n\napp/lib/courseCache.ts:22:14 - error TS7034: Variable 'cacheMap' implicitly has type 'any' in some locations\napp/api/attempts/[id]/answers/route.ts:41:22 - error TS2345: Argument of type 'string | null' is not assignable to parameter of type 'string'\napp/components/QuizNav.tsx:88:5 - warning: Static HTML elements with event handlers require a role (jsx-a11y/no-static-element-interactions)\napp/components/QuizNav.tsx:112:9 - warning: Visible, non-interactive elements with click handlers must have at least one keyboard listener\napp/lib/grades.ts:141:3 - error TS2554: Expected 2 arguments, but got 3\n\n3 errors, 2 warnings", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.3, "slice": "pasted-context", "lang": "en"}
{"prompt": "spotbugs on the WMS service, two of these look real:\n\nM C RCN: Nullcheck of value previously dereferenced in TrafficManager.tryReserve(String, String, Duration)\nM P UPM: Private method TaskDispatcher.requeue(Task) is never called\nH C IS2: Inconsistent synchronization of TrafficManager.reservations; locked 60% of time\nM D DM: TaskDispatcher.assign() invokes inefficient new String() constructor\nH C EC: Call to equals() comparing Robot and String in FleetRegistry.find(String)\n\n5 warnings, and IS2 on the reservations map is the one i keep thinking about", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.4, "slice": "pasted-context", "lang": "en"}
{"prompt": "index lifecycle policy versus what we actually keep, one of these is wrong:\n\nPUT _ilm/policy/edr-logs\n{\n \"policy\": {\n \"phases\": {\n \"hot\": { \"actions\": { \"rollover\": { \"max_primary_shard_size\": \"50gb\", \"max_age\": \"1d\" } } },\n \"warm\": { \"min_age\": \"7d\", \"actions\": { \"shrink\": { \"number_of_shards\": 1 } } },\n \"cold\": { \"min_age\": \"30d\", \"actions\": { \"searchable_snapshot\": { \"snapshot_repository\": \"s3\" } } },\n \"delete\": { \"min_age\": \"90d\", \"actions\": { \"delete\": {} } }\n }\n }\n}\n\nour contract with two customers says 12 months of searchable telemetry, and our marketing page says 13 months", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.35, "slice": "pasted-context", "lang": "en"}
{"prompt": "CDN config for lesson media, which is why one district gets no caching at all:\n\ncache_rules:\n - path: \"/media/*\"\n cache: { ttl: 604800, key: [path, query, header:Cookie, header:Origin] }\n - path: \"/api/*\"\n cache: { ttl: 0 }\n\norigin response headers:\n cache-control: public, max-age=604800\n vary: Origin, Accept-Encoding, Cookie\n\nthe media is identical for every student and requires a signed URL in the query string, which is already in the cache key", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.3, "slice": "pasted-context", "lang": "en"}
{"prompt": "kafka consumer settings, prod versus the values the vendor recommends:\n\n# ours\nsession.timeout.ms: 10000\nheartbeat.interval.ms: 3000\nmax.poll.interval.ms: 300000\ngroup.instance.id: unset\npartition.assignment.strategy: RangeAssignor\n\n# vendor's recommendation for mobile consumers\nsession.timeout.ms: 45000\nheartbeat.interval.ms: 15000\nmax.poll.interval.ms: 300000\ngroup.instance.id: <stable per robot>\npartition.assignment.strategy: CooperativeStickyAssignor\n\nour robots drop off wifi for 5-20 seconds when they pass through racking, and every drop triggers a full group rebalance", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.35, "slice": "pasted-context", "lang": "en"}
{"prompt": "les seuils d'alerte du WMS, on est réveillés pour rien mais on rate les vrais problèmes :\n\n- alert: ConsumerLag\n expr: kafka_consumergroup_lag{group=\"wms-robots\"} > 100\n for: 1m\n labels: { severity: page }\n\n- alert: RobotOffline\n expr: up{job=\"robot\"} == 0\n for: 0m\n labels: { severity: page }\n\n- alert: TaskDeadLettered\n expr: increase(wms_tasks_dead_lettered_total[1h]) > 0\n for: 0m\n labels: { severity: ticket }\n\nles robots passent hors ligne 5 à 20 secondes en traversant les rayonnages, le lag dépasse 100 à chaque vague de commandes, et le vrai incident de mai (une réservation libérée sous un robot en mouvement) n'a déclenché aucune alerte", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.4, "slice": "pasted-context", "lang": "fr"}
{"prompt": "this dispatcher has grown five responsibilities and a scheduled executor. same behaviour, separable pieces:\n\npublic class TaskDispatcher {\n // builds the pick list from open orders\n // chooses a robot by capability, distance and current load\n // produces to kafka and tracks the lease\n // requeues on missed ack, dead-letters after three attempts\n // emits metrics and writes an audit row per assignment\n // runs a scheduled sweep every second for expired leases\n}\n\n800 lines, one test that boots the whole spring context and a real kafka container, and the lease sweep is the part we most need to change", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "pasted-context", "lang": "en"}
{"prompt": "drei Stellen bauen dieselbe Prisma-Abfrage für „Kurse eines Lehrers\", leicht unterschiedlich:\n\n// app/api/courses/route.ts\nprisma.course.findMany({ where: { teacherId, archivedAt: null }, include: { assessments: true } })\n\n// app/dashboard/page.tsx\nprisma.course.findMany({ where: { teacherId }, include: { assessments: true, enrolments: true } })\n\n// lib/reports.ts\nprisma.$queryRaw`SELECT * FROM courses WHERE teacher_id = ${teacherId} AND archived_at IS NULL`\n\ndie zweite vergisst archivierte Kurse auszuschließen, die dritte umgeht das Row-Level-Security-Setup komplett", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "pasted-context", "lang": "de"}
{"prompt": "planning input for the term, and i need it sequenced against exam week:\n\n- exam week is in three weeks and lost answers are our most damaging bug\n- the instructor dashboard times out for our two largest institutions, both of whom are up for renewal\n- the WMS traffic manager has a safety-adjacent bug that legal wants addressed before the next site goes live\n- the SIEM's detection rules are noisy enough that the customer's SOC has started ignoring them\n- two engineers are shared across the LMS and the WMS, and neither product is moving\n- a customer wants 12 months of searchable telemetry, we currently delete at 90 days\n- there's a node major version upgrade we've deferred twice", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.9, "slice": "pasted-context", "lang": "en"}
{"prompt": "architecture ticket, and i want the thinking before anyone starts:\n\nWMS-702 — Safety-critical reservation handling\nThe traffic manager releases a node reservation when a robot's heartbeat is missed for 15 seconds, on the assumption that a silent robot has stopped. In May a robot passed through racking, lost wifi, kept moving, and its reservation was granted to another robot. Nobody was hurt and no goods were damaged. The proposal is to require positive confirmation of a stop before releasing, which means a robot that genuinely dies blocks its node until a human intervenes. Constraints: robots have no independent radio; the aisle e-stop is the only guaranteed stop; and throughput targets assume reservations are released within seconds.", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.95, "slice": "pasted-context", "lang": "en"}
{"prompt": "SIEM team's wishlist, one engineer, one quarter:\n\n- rule versioning, so an alert can be traced to the rule text that produced it\n- a test harness for rules against recorded telemetry, instead of writing to production\n- per-tenant thresholds, because absolute counts don't work across customers of different sizes\n- suppression that decays rather than a fixed one-hour window\n- retention to 12 months for two contracts, which is a storage and cost question as much as a technical one\n- the ingestion pipeline stops losing whole batches when elasticsearch rejects them\n\nwhat's the order, and which of these is secretly the biggest", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.85, "slice": "pasted-context", "lang": "en"}
{"prompt": "design spec for the quiz player, which has to work under exam conditions:\n\nQuiz player\n- One question per screen on mobile, optional all-questions view on desktop; the choice persists per student.\n- Question navigator: a grid of numbers, showing answered / unanswered / flagged, always reachable by keyboard.\n- Autosave indicator: a small text state — \"Saved 11:02\", \"Saving…\", \"Not saved — retrying\" — never a spinner that lies.\n- Offline: answers queue locally and the banner says exactly what is unsaved; the submit button is disabled while anything is queued.\n- Timer: fixed at the top, warns at five minutes and one minute, announced politely rather than continuously.\n- Submission: a confirmation listing unanswered questions, which is the only blocking dialog in the flow.\n- Everything keyboard operable, focus visible, and no interaction that requires a hover.\n- Must degrade to a plain form if JavaScript fails mid-exam, because it has happened.", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.8, "slice": "pasted-context", "lang": "en"}
{"prompt": "spec for the warehouse console's aisle view, which supervisors watch all shift:\n\nAisle view\n- Top-down schematic of one aisle, racking either side, robots as arrows showing heading, updating at 4Hz over websocket.\n- Node reservations drawn as translucent overlays with the holding robot's id; expiring reservations pulse in the last three seconds.\n- Robot cards along the right: id, battery, current task, lease remaining, last heartbeat age. Cards sort by problem state first.\n- A robot with a missed heartbeat is unmistakable — not just a colour, but a striped overlay and a persistent banner.\n- Controls: software pause per aisle, drain, and per-robot manual drive, all behind a role check with the button absent rather than disabled.\n- The e-stop state is displayed but never controllable from software.\n- Everything must be legible from two metres on a wall-mounted screen, and must not depend on hover for any information.", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.8, "slice": "pasted-context", "lang": "en"}
{"prompt": "accessibility audit of the LMS, which a district commissioned before renewal:\n\n1. Quiz question navigation is mouse-only; the number grid cannot be reached or operated by keyboard.\n2. The autosave state is conveyed by a coloured dot with no text alternative.\n3. The exam timer is announced by screen readers on every tick, making the page unusable.\n4. Drag-to-order questions have no keyboard alternative at all.\n5. Focus is lost to the document body after every question transition.\n6. Error messages on the submission dialog are not associated with the controls they refer to.\n7. Contrast on the \"flagged\" question state is 2.7:1 against the grid background.", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.75, "slice": "pasted-context", "lang": "en"}
{"prompt": "analyst console's alert triage screen, spec from the SOC team who use it eight hours a day:\n\nTriage view\n- Alert list on the left, virtualised, grouped by rule with counts; keyboard j/k moves, enter opens, e escalates, s suppresses.\n- Detail pane: the matched events in a table, the rule text as it was at match time, and the enrichment results with their source and age.\n- Enrichment that failed must say so explicitly rather than showing an empty field.\n- Timeline of related alerts for the same entity within 24 hours, on one axis, clickable.\n- Bulk actions on a selection, with an undo window of ten seconds rather than a confirmation dialog.\n- Every action records who, when and why; the why is a required free-text field for escalation and suppression.\n- Dark theme is the default because the SOC runs with the lights down, and both themes must pass contrast.", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.75, "slice": "pasted-context", "lang": "en"}
{"prompt": "integration spec a district's student information system expects from us:\n\nOneRoster 1.2 REST, we implement the consumer side\n GET /ims/oneroster/rostering/v1p2/orgs/{id}/classes paginated, up to 20k classes\n GET .../classes/{id}/students and .../classes/{id}/teachers\n sync nightly; the district publishes changes at 02:00 local time and expects us current by 07:00\n enrolment removals are soft — a student disappearing from a class must not delete their submissions\n the district's ids are opaque strings and are not stable across academic years\n they rate limit us to 10 requests per second and will not raise it\n a partial sync must be resumable, and a failed sync must not leave students without access at 08:00", "purpose": "backendImpl", "secondary": null, "mixed": false, "difficulty": 0.8, "slice": "pasted-context", "lang": "en"}
{"prompt": "schema we agreed for rule versioning, now it needs building:\n\nCREATE TABLE rule_versions (\n id uuid PRIMARY KEY,\n rule_id uuid NOT NULL,\n version int NOT NULL,\n body jsonb NOT NULL,\n author text NOT NULL,\n created_at timestamptz NOT NULL DEFAULT now(),\n active_from timestamptz,\n active_to timestamptz,\n UNIQUE (rule_id, version)\n);\n\nalerts must reference the rule_version that produced them; deleting a rule must not orphan alerts; an analyst editing a rule creates a new version rather than mutating; and the triage screen has to show the rule text as it was when the alert fired, which means versions are immutable once any alert references them", "purpose": "backendImpl", "secondary": null, "mixed": false, "difficulty": 0.75, "slice": "pasted-context", "lang": "en"}
{"prompt": "retention to 12 months on the EDR policy", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.25, "slice": "core", "lang": "en"}
{"prompt": "sharp bump before the freeze", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.2, "slice": "core", "lang": "en"}
{"prompt": "drop Cookie from the media cache key", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.3, "slice": "core", "lang": "en"}
{"prompt": "the console lets a supervisor drive a robot manually and i genuinely don't know what happens if they do that while the robot holds a node reservation and has an active task lease. work through the interaction between manual drive, the traffic manager and the dispatcher, and tell me which of the three thinks it is in charge", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.8, "slice": "core", "lang": "en"}
{"prompt": "our python services load configuration three different ways and the SIEM one reads environment variables at import time, which is why a config change needs a restart nobody expects. unify the loading, then document the new precedence so operators stop guessing", "purpose": "refactor", "secondary": "writing", "mixed": true, "difficulty": 0.6, "slice": "mixed", "lang": "en"}
{"prompt": "certificate email says \"Congradulations\"", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.1, "slice": "core", "lang": "en"}
{"prompt": "session timeout to 45s for the robots", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.3, "slice": "core", "lang": "en"}
{"prompt": "el botón de entrega sigue en inglés", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.15, "slice": "core", "lang": "es"}
{"prompt": "stable group.instance.id per robot", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.3, "slice": "boundary", "lang": "en"}
{"prompt": "rules should query logs-edr-* not logs-*", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.3, "slice": "boundary", "lang": "en"}
{"prompt": "add a timeout to the ASN lookup", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.25, "slice": "boundary", "lang": "en"}
{"prompt": "Kurs-Cache begrenzen, er wächst unbegrenzt", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.3, "slice": "boundary", "lang": "de"}
{"prompt": "RobotOffline needs a 30 second delay", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.25, "slice": "boundary", "lang": "en"}
{"prompt": "question navigator grid, keyboard operable", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.45, "slice": "core", "lang": "en"}
{"prompt": "autosave state needs text, not a dot", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.25, "slice": "core", "lang": "en"}
{"prompt": "reservation overlays on the aisle view", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "core", "lang": "en"}
{"prompt": "failed enrichment shows an empty field", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.3, "slice": "core", "lang": "en"}
{"prompt": "試験タイマーが毎秒読み上げられます", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.35, "slice": "core", "lang": "ja"}
{"prompt": "flagged state fails contrast", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.2, "slice": "boundary", "lang": "en"}
{"prompt": "focus is lost between questions", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.3, "slice": "boundary", "lang": "en"}
{"prompt": "pull the lease sweep out of the dispatcher", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.55, "slice": "core", "lang": "en"}
{"prompt": "une seule requête pour « cours du professeur »", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "core", "lang": "fr"}
{"prompt": "`enrolment` spelling, pick one", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.3, "slice": "boundary", "lang": "en"}
{"prompt": "extract the rule query builder", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "boundary", "lang": "en"}
{"prompt": "inline the single-use `scoreFor`", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.2, "slice": "boundary", "lang": "en"}
{"prompt": "docstrings for the task lease API", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.4, "slice": "core", "lang": "en"}
{"prompt": "release notes for LMS 6.4", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.3, "slice": "core", "lang": "en"}
{"prompt": "nota para as escolas sobre as notas", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.4, "slice": "core", "lang": "pt"}
{"prompt": "document the auto-submit job for teachers", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.4, "slice": "boundary", "lang": "en"}
{"prompt": "summarise the reservation proposal", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "boundary", "lang": "en"}
{"prompt": "PR body for the grading unification", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.3, "slice": "boundary", "lang": "en"}
{"prompt": "can a reservation outlive a moving robot?", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.85, "slice": "core", "lang": "en"}
{"prompt": "¿por qué las reglas dejaron de disparar?", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "core", "lang": "es"}
{"prompt": "walk me through the nightly auto-submit", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "boundary", "lang": "en"}
{"prompt": "answers disappear from the review screen", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "core", "lang": "en"}
{"prompt": "elasticsearch rejects our morning writes", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "boundary", "lang": "en"}
{"prompt": "warum wächst der Heap bis zum Neustart?", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.65, "slice": "boundary", "lang": "de"}
{"prompt": "endpoint for a rule's version history", "purpose": "backendImpl", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "core", "lang": "en"}
{"prompt": "onwards with that", "purpose": "backendImpl", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "vague-eval", "lang": "en"}
{"prompt": "calmer alerts", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.45, "slice": "vague-eval", "lang": "en"}
{"prompt": "whatever helps before exams", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "vague-eval", "lang": "en"}
{"prompt": "neaten it up", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.4, "slice": "vague-eval", "lang": "en"}
{"prompt": "like last week", "purpose": "backendImpl", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "vague-eval", "lang": "en"}
{"prompt": "audit answers", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "vague-eval", "lang": "en"}
{"prompt": "encore le tableau de bord", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "vague-eval", "lang": "fr"}
{"prompt": "something quick", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.4, "slice": "vague-eval", "lang": "en"}
{"prompt": "give it another read", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.45, "slice": "vague-eval", "lang": "en"}
{"prompt": "優先度はお任せします", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "vague-eval", "lang": "ja"}
{"prompt": "usual for this sprint", "purpose": "backendImpl", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "vague-eval", "lang": "en"}
{"prompt": "traffic manager releases a node reservation when a robot's heartbeat has been missing for fifteen seconds, on the assumption that a silent robot has stopped, and in May that assumption was wrong in the most alarming possible way. i want the options for making this safe worked through properly — positive stop confirmation, independent sensing, aisle-level interlocks — with an honest view of what each does to throughput and what happens when a robot genuinely dies mid-aisle legal has asked for this in writing before the next site goes live, so the reasoning matters as much as the answer.", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.95, "slice": "core", "lang": "en"}
{"prompt": "SOC has started ignoring our alerts, which makes the whole product pointless regardless of how good the detection is. work through what would actually restore trust — rule versioning, testing against recorded telemetry, per-tenant thresholds, decaying suppression — and tell me which of those is secretly the biggest piece of work rather than the most obviously useful their own metric is alerts investigated per shift, which has halved since january.", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.85, "slice": "core", "lang": "en"}
{"prompt": "two of our contracts promise twelve months of searchable telemetry and our lifecycle policy deletes at ninety days, which somebody is going to notice during an investigation rather than during a review. work out what twelve months actually costs across hot, warm and cold tiers at our current volume, and what the honest options are including renegotiating", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.8, "slice": "boundary", "lang": "en"}
{"prompt": "analysts write detection rules by copying blog posts and seeing what fires in production, which is how we ended up with forty false positives a day from one rule. write the rule-authoring guide — ownership, rationale, expected volume, suppression, thresholds, testing — aimed at analysts who write rules but never operate the platform the SMB rule is the example everyone recognises, so it's worth walking through it.", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "core", "lang": "en"}
{"prompt": "detection rules stopped generating alerts overnight and the only unusual event was tomorrow's index being created at seven minutes past two. work through how the rules resolve indices and time windows, and tell me whether that index explains it or whether it's a coincidence i've latched onto the deployment spans three timezones, if that turns out to matter.", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.8, "slice": "boundary", "lang": "en"}
{"prompt": "enrichment providers each invent their own failure handling — one has no timeout, one silently returns nothing, one sleeps ten seconds inside the pipeline, one throws and kills the batch. give them one interface with explicit timeouts and failure semantics, keeping each provider's successful output exactly as it is today the ASN provider is the one currently taking the pipeline down, so start the analysis there.", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "core", "lang": "en"}
{"prompt": "inventory drifts by a few units a day and the two picks in the sample were dispatched from the same snapshot of five units, which smells like the dispatcher reading availability without reserving it. work through the ordering of the task, the pick and the inventory event before we propose anything reconciliation runs at eighteen hundred and the discrepancies are always small and always negative.", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.85, "slice": "core", "lang": "en"}
{"prompt": "aisle view is what supervisors watch all shift and it currently conveys a missed heartbeat with a colour change nobody notices from two metres. build the view to the new spec, with the problem states unmistakable and the e-stop state visible but never controllable from software the screens are wall-mounted at about two metres and nobody is going to hover over anything.", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "boundary", "lang": "en"}
{"prompt": "before we touch the traffic manager i want the safety argument written down — what we assume, what guarantees each layer provides, where a single failure is tolerated — and then the heartbeat handling changed to whatever that argument says is defensible the May near-miss is the case the argument has to explain, not just the happy path.", "purpose": "planning", "secondary": "backendImpl", "mixed": true, "difficulty": 0.95, "slice": "mixed", "lang": "en"}
{"prompt": "attempt model needs to handle two devices and flaky connections properly, which is a design question, and it needs to stop losing answers before exams, which is urgent. do the design first, then the idempotent answer write against it students routinely start on a laptop and finish on a phone, which nobody designed for.", "purpose": "planning", "secondary": "backendImpl", "mixed": true, "difficulty": 0.85, "slice": "mixed", "lang": "en"}
{"prompt": "die Anreicherungspipeline blockiert regelmäßig komplett, wenn ein Anbieter langsam ist. Ich hätte gern zuerst ein Konzept für Timeouts, Nebenläufigkeit und Rückstau und danach die Umsetzung für den ASN-Anbieter, weil der uns gerade am häufigsten umbringt", "purpose": "planning", "secondary": "backendImpl", "mixed": true, "difficulty": 0.75, "slice": "mixed", "lang": "de"}
{"prompt": "teachers need the attempts page written for them before exam week, and writing it will make obvious which parts are product bugs rather than missing documentation. produce the page, and give me the separate list of things we should fix instead of explaining last term generated forty support tickets, most of them the same three questions.", "purpose": "writing", "secondary": "review", "mixed": true, "difficulty": 0.6, "slice": "mixed", "lang": "en"}
{"prompt": "escribe la documentación del motor de reglas para los analistas y comprueba en el código si la ventana de supresión es realmente fija en una hora, porque el equipo cree que es configurable", "purpose": "writing", "secondary": "review", "mixed": true, "difficulty": 0.6, "slice": "mixed", "lang": "es"}
{"prompt": "warehouse runbook needs writing and the aisle-drain procedure needs fixing, because draining an aisle with robots inside is currently possible from the console. write the runbook, then put the guard in", "purpose": "writing", "secondary": "backendImpl", "mixed": true, "difficulty": 0.65, "slice": "mixed", "lang": "en"}
{"prompt": "task dispatcher does five things and the lease sweep is the one we need to change for safety reasons. separate them, then document the new boundaries so the next change doesn't have to understand all five", "purpose": "refactor", "secondary": "writing", "mixed": true, "difficulty": 0.7, "slice": "mixed", "lang": "en"}
{"prompt": "rule engine's three query syntaxes should become one. migrate the existing rules, and write the note explaining to analysts what changed and which of their rules were rewritten", "purpose": "refactor", "secondary": "writing", "mixed": true, "difficulty": 0.7, "slice": "mixed", "lang": "en"}
{"prompt": "one district gets no CDN caching on lesson media and the Vary header is the obvious suspect, but their proxy adds a Cookie to every request so it may be their side. confirm which it is, then fix whichever end we control every other district on the same build is fine, which is what makes me suspect their proxy.", "purpose": "debugging", "secondary": "quickFix", "mixed": true, "difficulty": 0.65, "slice": "mixed", "lang": "en"}
{"prompt": "robots rebalance constantly and one aisle periodically stops receiving tasks, which i think are the same problem. diagnose it properly, then change the consumer configuration to whatever the diagnosis says rather than what the vendor's blog recommends", "purpose": "debugging", "secondary": "quickFix", "mixed": true, "difficulty": 0.8, "slice": "mixed", "lang": "en"}
{"prompt": "triage screen needs bulk actions with an undo window, and the SOC wants to know what \"undo\" means for an escalation that already paged someone. design that interaction with me, then build it", "purpose": "frontendImpl", "secondary": "planning", "mixed": true, "difficulty": 0.65, "slice": "mixed", "lang": "en"}
{"prompt": "npm audit has one severe finding whose fix is a major version we can't take three weeks before exams. work out the exposure honestly, apply what's safe, and tell me what compensating control covers the rest", "purpose": "quickFix", "secondary": "review", "mixed": true, "difficulty": 0.55, "slice": "mixed", "lang": "en"}
{"prompt": "per-tenant thresholds need to exist before the next customer onboards, and the shape matters — absolute, relative to baseline, or both. decide with me, then implement", "purpose": "backendImpl", "secondary": "planning", "mixed": true, "difficulty": 0.7, "slice": "mixed", "lang": "en"}
{"prompt": "rename `Task` in the WMS service, it collides with the scheduler's Task and the API's TaskDto", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.45, "slice": "boundary", "lang": "en"}
{"prompt": "could you explain what happens to an attempt when a student opens the same quiz on a second device", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "core", "lang": "en"}
{"prompt": "why does our SMB rule fire forty times a day from the same six servers", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "boundary", "lang": "en"}
{"prompt": "someone should check whether an analyst can delete an alert without leaving a trace", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "boundary", "lang": "en"}
{"prompt": "is it expected that a robot keeps executing a task it can no longer report progress on", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.75, "slice": "boundary", "lang": "en"}
{"prompt": "docs/attempts.md says answers are upserted, which stopped being true in the rewrite", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.4, "slice": "core", "lang": "en"}
{"prompt": "a short note explaining why the lease sweep is moving out of the dispatcher, for the decision log", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.35, "slice": "core", "lang": "en"}
{"prompt": "API changelog needs an entry for institution-scoped tokens and what they replace", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.4, "slice": "boundary", "lang": "en"}
{"prompt": "javadoc on tryReserve promises exclusivity that the sweep thread quietly breaks", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "boundary", "lang": "en"}
{"prompt": "write the customer note about telemetry retention changing from 90 days to 12 months", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.4, "slice": "boundary", "lang": "en"}
{"prompt": "precisamos de uma página que explique aos professores como funcionam as tentativas", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.45, "slice": "boundary", "lang": "pt"}
{"prompt": "health endpoint reports the rules engine healthy while it has produced zero alerts for six hours", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.35, "slice": "core", "lang": "en"}
{"prompt": "dead-letter alert only fires on an increase over an hour, so a steady trickle is invisible", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.3, "slice": "boundary", "lang": "en"}
{"prompt": "how should we handle student ids that change between academic years without losing submission history", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.75, "slice": "core", "lang": "en"}
{"prompt": "what's the right way to test the traffic manager, given that the failure mode is two robots in one place", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.85, "slice": "core", "lang": "en"}
{"prompt": "i want a position on whether detection rules belong in git or in the database now that they need versions", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "core", "lang": "en"}
{"prompt": "three districts want single sign-on with three different identity providers, what should our approach be", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "boundary", "lang": "en"}
{"prompt": "what should happen to alerts when a customer offboards, given the contract says we delete their data", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.65, "slice": "boundary", "lang": "en"}
{"prompt": "an endpoint that returns an attempt's full answer history including superseded values, for teachers", "purpose": "backendImpl", "secondary": null, "mixed": false, "difficulty": 0.55, "slice": "core", "lang": "en"}
{"prompt": "bulk indexer should check per-item responses and retry only the rejected documents", "purpose": "backendImpl", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "boundary", "lang": "en"}
{"prompt": "alert timeline should show related alerts for the same entity within 24 hours on one axis", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.55, "slice": "core", "lang": "en"}
{"prompt": "instructor dashboard needs a loading skeleton that doesn't shift the layout when data arrives", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.4, "slice": "core", "lang": "en"}
{"prompt": "robot cards should show lease remaining as a countdown rather than an absolute timestamp", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.4, "slice": "boundary", "lang": "en"}
{"prompt": "quiz submission dialog should list unanswered questions as links, not just a count", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.45, "slice": "boundary", "lang": "en"}
{"prompt": "anything that survives exam week", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.45, "slice": "vague-eval", "lang": "en"}
{"prompt": "back to the rules engine", "purpose": "backendImpl", "secondary": null, "mixed": false, "difficulty": 0.55, "slice": "vague-eval", "lang": "en"}
{"prompt": "i'd like to understand what happens to a task lease when kafka rebalances mid-execution, because a robot that keeps working while its partition moves is exactly the shape of the aisle-stall bug. trace the interaction properly and tell me whether the lease and the partition assignment can ever disagree about who owns a task", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.8, "slice": "boundary", "lang": "en"}
{"prompt": "submissions need a client-supplied idempotency key so that a retry on a slow connection cannot create a second answer row, which is the mechanism behind the answers students say disappear. design the key's scope and lifetime, implement the write path, and make sure an old client without the header still works during exam week", "purpose": "backendImpl", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "core", "lang": "en"}
{"prompt": "exam week needs the health endpoint to stop lying about the rules engine, and it needs an alert when zero alerts have been produced for an hour. do both, and tell me what else in our monitoring reports healthy while producing nothing", "purpose": "quickFix", "secondary": "review", "mixed": true, "difficulty": 0.5, "slice": "mixed", "lang": "en"}
{"prompt": "nobody has been able to tell me what the grading worker does when an assessment's weight changes after grades have been published — whether it recalculates silently, waits for the nightly run, or leaves the published grade alone. read the recalculation path and the nightly job together and tell me what a student would actually see in each case", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.65, "slice": "core", "lang": "en"}
{"prompt": "our LMS notification code sends email, in-app and push from three different places with three different templating approaches, and a student who has muted a course still gets the push. bring them behind one notification service with preferences applied in one place, keeping every existing message identical in wording and timing", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.65, "slice": "core", "lang": "en"}
{"prompt": "the SIEM's alert model carries both the matched documents and a denormalised copy of the entity fields, which have drifted apart since the enrichment rewrite. settle on one representation, migrate the existing alerts, and keep the triage screen showing exactly what it shows today for alerts that predate the change", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "core", "lang": "en"}
{"prompt": "we need an endpoint that returns a student's full submission history for a course, including superseded answers and the attempt each came from, because teachers currently ask support for a database export. it has to be paginated, cheap enough to call from the teacher's screen, and must not expose other students' data through a guessable id", "purpose": "backendImpl", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "core", "lang": "en"}
{"prompt":"Split projects/isotope/ml/pipeline/features.py by responsibility, not file length: isolate parsing, validation, and persistence while leaving the exported surface and call sequence untouched.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"}
{"prompt":"UI ticket DES-49139: finish the compact IsotopeHarborIndexFlow filter experience\n\nRoute: /catalog/search\nSource: projects/isotope/ui/settings/PrivacyPane.tsx\nFramework: Tokio\n\nCurrent QA notes\n- at 390 px the filter sheet is wider than the viewport by 16 px\n- returning from background selects segment four while the visible chip says three\n- keyboard focus falls behind the sheet after Apply\n- VoiceOver announces the internal value `sync_state_retriable`\n- the loading spinner never resolves into an offline action\n- dark appearance uses the light divider token\n- Reduce Motion still runs the spring transition\n- at accessibility XXXL the footer buttons overlap\n\nBrowser console during the transition:\n[ui] sheet.presented source=toolbar selected=3\n[ui] scene.inactive cachedSelection=3\n[ui] scene.active restoredSelection=4\n[ui] focus.restore target=filter-button result=detached\n[ui] network.status value=offline renderedState=loading\n\nAcceptance criteria from design\nThe phone layout should use an edge-to-edge sheet; tablet keeps the anchored panel. Applying filters returns focus to the opener and announces the result count. Empty, offline, retrying, and loaded states must be visually distinct. Use existing design tokens, support keyboard escape, preserve current data requests, and provide a no-animation path when Reduce Motion is enabled.\n\nFinish the visible IsotopeHarborIndexFlow state described above: responsive layout, correct selection restoration, keyboard focus, accessible labels, dark mode, and reduced-motion behavior.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"}
{"prompt":"IsotopeSummitProxyCoordinator: restructure, then assess","purpose":"refactor","secondary":"review","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"}
{"prompt":"Center the IsotopeAmberFilterService modal","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"boundary","lang":"en"}
{"prompt":"Walk through IsotopeIrisBatchStore's SyncWorker.kt","purpose":"review","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"}
{"prompt":"diff --git a/projects/isotope/Sources/App/SessionStore.swift b/projects/isotope/Sources/App/SessionStore.swift\nindex 62d71aa..90f3c1e 100644\n--- a/projects/isotope/Sources/App/SessionStore.swift\n+++ b/projects/isotope/Sources/App/SessionStore.swift\n@@ -41,18 +41,27 @@ export async function reconcile(input: Batch) {\n- const rows = input.items.map(normalize);\n- await store.write(rows);\n- await metrics.count(\"reconciled\", rows.length);\n+ const scope = tracer.startActiveSpan(\"reconcile\");\n+ try {\n+ const rows = input.items.map(normalize);\n+ await Promise.all([\n+ store.write(rows),\n+ metrics.count(\"reconciled\", rows.length),\n+ ]);\n+ return { cursor: input.next, count: rows.length };\n+ } finally {\n+ scope.end();\n+ }\n }\n\n@@ -88,7 +97,11 @@ function normalize(item: WireItem): Row {\n- return { id: item.id, value: item.payload ?? \"\" };\n+ return {\n+ id: item.id.trim(),\n+ value: item.payload?.normalize(\"NFC\") ?? \"\",\n+ receivedAt: clock.now(),\n+ };\n }\n\nPR note: staging p95 drops by 18 ms. Tests assert row counts but not whether metrics happen before the durable write.\n\nRestructure IsotopeCloudReconcilerFlow so duplicated normalization and shutdown ownership have one home. Preserve public behavior, wire values, logging fields, and ordering; extend characterization coverage first.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"}
{"prompt":"Wire a IsotopeFlintTimelineFlow background task in projects/isotope/services/ledger/replay.go that expires abandoned sessions, records an OpenTelemetry span, and yields cleanly when shutdown begins.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"}
{"prompt":"Production says IsotopeFlintTimelineService is healthy while users see stalled work, and the current telemetry does not reveal which ownership boundary lost progress. Correlate the queue, scheduler, storage, and shutdown paths; form competing hypotheses, identify evidence for each, and narrow the root cause before proposing a code change.\n\nConstraints:\n- touch generated artifacts only through their checked-in generator\n- keep the patch readable for a small on-call review\n- retain the current PostgreSQL 17 operational envelope\n\nThis repository spans media encoding, Python ML, Windows; use its existing conventions rather than importing a new abstraction.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"}
{"prompt":"Cinder: The IsotopeLedgerGateService feature flag default should be false in test, exactly like production; correct that config entry and nothing else.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"}
{"prompt":"IsotopeSableParserCoordinator: rethink this area","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"}
{"prompt":"Teach IsotopeOpalRouterStore to verify signed continuation tokens, reject cross-tenant cursors, and rotate keys without invalidating tokens issued during the overlap window.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"}
{"prompt":"// projects/isotope/crates/index/src/segment.rs\nfinal class IsotopeBeaconStoreFlowCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task<Void, Never>] = [:]\n\n func accept(_ event: Event) {\n pending[event.id]?.cancel()\n pending[event.id] = Task {\n let normalized = normalize(event)\n try? await store.persist(normalized)\n await MainActor.run {\n NotificationCenter.default.post(\n name: .eventDidPersist,\n object: event.id\n )\n }\n }\n }\n\n func stop() {\n pending.values.forEach { $0.cancel() }\n pending.removeAll()\n }\n}\n\n// A second copy lives in PreviewCoordinator.swift. It uses the same normalization\n// rules but calls store.persist before assigning the Task into `pending`.\n\nTests currently cover successful persistence and explicit stop. They do not cover replacement of an in-flight event with the same ID, cancellation thrown by the store, or whether the notification may arrive after stop returns. Public callers rely on accept being synchronous.\n\nWalk through what the artifact proves about IsotopeBeaconStoreFlow; flag semantic changes and missing coverage with exact evidence, keeping this a read-only pass.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"}
{"prompt":"Could IsotopeNovaPickerService show the active NATS JetStream sync phase as an accessible progress row, including reduced-motion behavior?","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"}
{"prompt":"IsotopeKiteSchedulerCoordinator: correct, then assess","purpose":"debugging","secondary":"review","mixed":true,"difficulty":0.5,"slice":"mixed","lang":"en"}
{"prompt":"Delta: projects/isotope/packages/api/openapi.yaml の IsotopeGarnetModalFlow で、NATS JetStream の flow に断続的な問題が起きています。 責務を分離して重複をなくし、API、wire value、順序、観測可能な動作は変えないでください。\n\n制約:\n- NATS JetStream を継続利用\n- 互換性と cancel の意味を維持\n- 変更範囲は IsotopeGarnetModalFlow のみ","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"ja"}
{"prompt":"Ember: Incident timeline — INC-49124\n\n08:02 deploy IsotopeAmberFilterFlow 6.18.0 begins in eu-west\n08:06 write latency rises from 22 ms to 410 ms; error rate remains below 0.2%\n08:08 autoscaler adds three workers; queue lag continues rising\n08:11 on-call disables feature flag `parallel_commit_v2`\n08:13 latency returns to 31 ms, but duplicate-event warnings increase\n08:19 traffic moved to the previous worker pool\n08:27 queue lag clears; no customer data loss observed\n\nWhat changed\nThe release moved metrics emission into the same Promise.all as the durable write and added NFC normalization to event payloads. Database CPU peaked at 64%, Redis stayed normal, and the downstream consumer reported 183 duplicate keys that its uniqueness constraint ignored.\n\nConstraints from incident command\n- no emergency schema change\n- preserve tenant ordering\n- canary must include a forced consumer rebalance\n- rollback decision must use two independent signals\n- ownership between storage and ingestion teams must be explicit\n\nThe next regular release window is in six days.\n\nDetermine why IsotopeAmberFilterFlow produces this result. Trace ordering, cancellation, shared state, and scheduler behavior; identify the root cause before suggesting a patch.","purpose":"debugging","secondary":"planning","mixed":true,"difficulty":0.9,"slice":"mixed","lang":"en"}
{"prompt":"diff --git a/projects/isotope/Sources/CLI/Commands/Doctor.swift b/projects/isotope/Sources/CLI/Commands/Doctor.swift\nindex 62d71aa..90f3c1e 100644\n--- a/projects/isotope/Sources/CLI/Commands/Doctor.swift\n+++ b/projects/isotope/Sources/CLI/Commands/Doctor.swift\n@@ -41,18 +41,27 @@ export async function reconcile(input: Batch) {\n- const rows = input.items.map(normalize);\n- await store.write(rows);\n- await metrics.count(\"reconciled\", rows.length);\n+ const scope = tracer.startActiveSpan(\"reconcile\");\n+ try {\n+ const rows = input.items.map(normalize);\n+ await Promise.all([\n+ store.write(rows),\n+ metrics.count(\"reconciled\", rows.length),\n+ ]);\n+ return { cursor: input.next, count: rows.length };\n+ } finally {\n+ scope.end();\n+ }\n }\n\n@@ -88,7 +97,11 @@ function normalize(item: WireItem): Row {\n- return { id: item.id, value: item.payload ?? \"\" };\n+ return {\n+ id: item.id.trim(),\n+ value: item.payload?.normalize(\"NFC\") ?? \"\",\n+ receivedAt: clock.now(),\n+ };\n }\n\nPR note: staging p95 drops by 18 ms. Tests assert row counts but not whether metrics happen before the durable write.\n\nSplit IsotopeSlateEditorFlow by responsibility and make cancellation ownership explicit. Characterize the current sequence before moving code and keep callers unchanged.","purpose":"refactor","secondary":"review","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"}
{"prompt":"PM needs a concise migration note for IsotopeCloudReconcilerStore, including the user impact, rollback trigger, and the one configuration key operators must change.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"}
{"prompt":"IsotopeWrenExportCoordinator needs a paired pass: produce a consumer guide for IsotopeWrenExportCoordinator, plus give the existing implementation a read-only safety pass. Use projects/isotope/db/migrations/20260730_events.sql as the source of truth, preserve the SQLite contract, and avoid unrelated cleanup.","purpose":"writing","secondary":"review","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"}
{"prompt":"Frost: The first IsotopeBirchMigratorFlow request after credential refresh gets 401, while an immediate retry succeeds. Follow token publication and request capture timing before recommending a fix.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"}
{"prompt":"Garnet: Two asks around IsotopeAmberFilterCoordinator: (1) separate IsotopeAmberFilterCoordinator's policy from transport without behavior changes; (2) capture the contract and rollback note for consumers. Keep the patch readable for a small on-call review, and leave a clear boundary between the resulting artifacts or edits.","purpose":"refactor","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"}
{"prompt":"A previously stable test around IsotopeDeltaCanvasFlow now fails one run in twenty. Determine whether ordering, locale, or leaked state is responsible.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"}
{"prompt":"IsotopeMosaicGridCoordinator: polish, then assess","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"}
{"prompt":"Harbor: Two asks around IsotopeFernSnapshotCoordinator: (1) assess ownership and failure handling in projects/isotope/apps/console/routes/usage.svelte; (2) capture the contract and rollback note for consumers. Keep the patch readable for a small on-call review, and leave a clear boundary between the resulting artifacts or edits.","purpose":"review","secondary":"writing","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"}
{"prompt":"Ticket OPS-49148: retire the legacy replay path for IsotopePrismCacheFlow\n\nBackground\nThe mobile clients now send monotonic cursors, but the worker still supports the pre-2024 offset token. That compatibility branch performs an extra database lookup on every page and owns a separate retry counter. Support confirmed that the oldest active client is version 8.14, which uses cursors.\n\nAcceptance notes\n- existing cursor tokens must remain valid during a two-release overlap\n- operators need one metric showing legacy traffic by client version\n- a rollback must not require restoring deleted columns\n- tenant isolation remains enforced in the storage query\n- SDK examples should show how to persist the continuation token\n- the public route and current 429 envelope cannot change\n\nOpen questions\nDo we delete the offset decoder immediately or quarantine it behind a flag? Who owns the mobile version gate? Can the database index be removed in the same deploy? Security wants evidence that forged cursors cannot select another tenant.\n\nSlack excerpt\nMina 09:42: “I can provide client adoption numbers, but not a guarantee about sideloaded builds.”\nRavi 09:47: “Please make the rollback trigger explicit; queue lag alone is too noisy.”\n\nTurn the material above into a concise IsotopePrismCacheFlow release note and operator runbook section. State impact, detection, rollback, and the client-visible contract; do not modify code.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"pasted-context","lang":"en"}
{"prompt":"Split IsotopeOrbitSyncService without behavior changes","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"}
{"prompt":"Clarify IsotopeMapleQueueService's retry docs","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"}
{"prompt":"Compare IsotopeMosaicGridStore's two adapters","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"}
{"prompt":"Translate the IsotopeEchoRegistryService setup notes","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"}
{"prompt":"The minimum supported WebGPU version in projects/isotope/Sources/App/SessionStore.swift is one patch behind the lockfile. Align that single value and regenerate only the affected metadata.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"}
{"prompt":"Fresh release brief for IsotopeDriftConsoleCoordinator:\n- primary outcome: find the unknown cause of stale cursors when a page is resumed\n- companion outcome: correct the known stale timeout beside it\n- repository entry point: projects/isotope/services/ledger/replay.go\n- platform constraint: PostgreSQL 17\n- known complication: stale cursors when a page is resumed\n\nBoth results are required, but they should remain independently reviewable. Keep the patch readable for a small on-call review; retain serialization and authorization boundaries; cover cancellation, idempotent retries, and rollback; and avoid drive-by cleanup. Use the code as the source of truth, call out assumptions, and state how an on-call engineer can tell that either part is unsafe to ship.","purpose":"debugging","secondary":"quickFix","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"}
{"prompt":"UI ticket DES-49159: finish the compact IsotopeBirchMigratorCoordinator filter experience\n\nRoute: /catalog/search\nSource: projects/isotope/ui/settings/PrivacyPane.tsx\nFramework: Tokio\n\nCurrent QA notes\n- at 390 px the filter sheet is wider than the viewport by 16 px\n- returning from background selects segment four while the visible chip says three\n- keyboard focus falls behind the sheet after Apply\n- VoiceOver announces the internal value `sync_state_retriable`\n- the loading spinner never resolves into an offline action\n- dark appearance uses the light divider token\n- Reduce Motion still runs the spring transition\n- at accessibility XXXL the footer buttons overlap\n\nBrowser console during the transition:\n[ui] sheet.presented source=toolbar selected=3\n[ui] scene.inactive cachedSelection=3\n[ui] scene.active restoredSelection=4\n[ui] focus.restore target=filter-button result=detached\n[ui] network.status value=offline renderedState=loading\n\nAcceptance criteria from design\nThe phone layout should use an edge-to-edge sheet; tablet keeps the anchored panel. Applying filters returns focus to the opener and announces the result count. Empty, offline, retrying, and loaded states must be visually distinct. Use existing design tokens, support keyboard escape, preserve current data requests, and provide a no-animation path when Reduce Motion is enabled.\n\nBring IsotopeBirchMigratorCoordinator's sheet to release quality across phone and tablet layouts; preserve its data flow while correcting selection, keyboard, VoiceOver, and animation states.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"}
{"prompt":"IsotopeRavenSessionStore has four wrappers that only translate the same error enum. Collapse them into one adapter and preserve every public case, message, and metric label.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"}
{"prompt":"Two engineers disagree about whether IsotopeCinderAuthFlow's cache is authoritative. Walk the reads and writes in projects/isotope/cmd/exporter/main.py and settle that question from the code. Nothing is reported broken, so keep this to an explanation of current behavior.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"}
{"prompt":"Iris: Split projects/isotope/config/staging.toml by responsibility, not file length: isolate parsing, validation, and persistence while leaving the exported surface and call sequence untouched.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"}
{"prompt":"Juniper: The public surface of IsotopeMapleQueueStore is frozen, but its internal ownership in projects/isotope/crates/index/src/segment.rs is difficult to test and even harder to change safely. Introduce one ownership boundary for storage and scheduling, collapse pass-through wrappers, and characterize ordering and cancellation before moving code.\n\nConstraints:\n- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside IsotopeMapleQueueStore\n- keep the patch readable for a small on-call review\n\nSeveral teams work in this media encoding, Python ML, Windows monorepo, so keep ownership and handoff points understandable in a small review.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"}
{"prompt":"Two asks around IsotopeQuartzPlayerCoordinator: (1) lay out a staged migration for IsotopeQuartzPlayerCoordinator; (2) then implement the bounded durable-cursor handler. Keep the patch readable for a small on-call review, and leave a clear boundary between the resulting artifacts or edits.","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"}
{"prompt":"Does IsotopeCopperBridgeStore enforce tenant scope before decoding its cursor, and could any early-return path reveal whether a foreign record exists? Nothing is reported broken, so keep this to an explanation of current behavior.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"}
{"prompt":"We need to move IsotopeTideWorkerService from the legacy store to Tokio. Propose phases, compatibility seams, metrics, rollback points, and the order in which clients should migrate; no code yet.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"}
{"prompt":"Responsive layout for IsotopeAcornWidgetStore","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"}
{"prompt":"IsotopeLedgerGateCoordinator: make this less weird","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"}
{"prompt":"IsotopeSpruceDaemonCoordinator is blocking the next release because duplicate retries after a network handoff. I need two concrete outcomes from a single pass: find the unknown cause of duplicate retries after a network handoff, and capture the contract and rollback note for consumers. Use the existing PostgreSQL 17 conventions in projects/isotope/internal/auth/refresh.go; keep the patch readable for a small on-call review. Keep the outcomes distinct so reviewers can see which evidence supports the assessment and which files or prose satisfy the requested change.\n\nConstraints:\n- preserve public wire values and tenant boundaries\n- cover cancellation and retry behavior\n- avoid generated code and unrelated cleanup\n- include a rollback trigger that an on-call engineer can measure\n\nThis is a fresh workstream for the release, so derive everything from the repository and the context here.","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"}
{"prompt":"Incident timeline — INC-49113\n\n08:02 deploy IsotopeWillowCodecFlow 6.18.0 begins in eu-west\n08:06 write latency rises from 22 ms to 410 ms; error rate remains below 0.2%\n08:08 autoscaler adds three workers; queue lag continues rising\n08:11 on-call disables feature flag `parallel_commit_v2`\n08:13 latency returns to 31 ms, but duplicate-event warnings increase\n08:19 traffic moved to the previous worker pool\n08:27 queue lag clears; no customer data loss observed\n\nWhat changed\nThe release moved metrics emission into the same Promise.all as the durable write and added NFC normalization to event payloads. Database CPU peaked at 64%, Redis stayed normal, and the downstream consumer reported 183 duplicate keys that its uniqueness constraint ignored.\n\nConstraints from incident command\n- no emergency schema change\n- preserve tenant ordering\n- canary must include a forced consumer rebalance\n- rollback decision must use two independent signals\n- ownership between storage and ingestion teams must be explicit\n\nThe next regular release window is in six days.\n\nCon este contexto, resuelve la petición indicada manteniendo API, compatibilidad y rollback; deja claras las decisiones y la evidencia. From this evidence, draft consumer-facing migration guidance for IsotopeWillowCodecFlow, plus a short operational recovery note. Keep uncertainty explicit and leave the implementation untouched.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"pasted-context","lang":"en"}
{"prompt":"IsotopeCraneWorkspaceCoordinator: untangle the messy bit","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"}
{"prompt":"Add a bounded IsotopeCloudReconcilerService export stream that resumes from checkpoints, respects cancellation, and exposes queue lag plus terminal failure counters.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"}
{"prompt":"Add a bounded IsotopePineMetricsService export stream that resumes from checkpoints, respects cancellation, and exposes queue lag plus terminal failure counters.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"}
{"prompt":"Compare IsotopeIrisBatchService's two adapters","purpose":"review","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"}
{"prompt":"Test Suite 'IsotopeWrenExportFlowTests' started at 2026-07-30 09:22:14.018\nTest Case '-[IsotopeWrenExportFlowTests testRestoresSelectionAfterBackgrounding]' started.\nprojects/isotope/src/sync/reconcile.ts:144: error: -[IsotopeWrenExportFlowTests testRestoresSelectionAfterBackgrounding] : XCTAssertEqual failed: (\"Optional(4)\") is not equal to (\"Optional(3)\")\nAccessibility hierarchy at failure:\n Application, 0x104c, pid: 812\n Window, identifier: \"main\"\n NavigationStack, identifier: \"catalog\"\n Button, label: \"Filters\", value: \"2 active\"\n CollectionView, identifier: \"results-grid\", rows: 24\n Sheet, identifier: \"filter-sheet\"\n TextField, label: \"Search filters\", value: \"\"\n Switch, label: \"Available offline\", value: \"1\"\n Button, label: \"Apply\", enabled: true\nTest Case '-[IsotopeWrenExportFlowTests testRestoresSelectionAfterBackgrounding]' failed (4.812 seconds).\n\nSimulator: iPhone 17 Pro, iOS 27.0, en_US, content size XXXL, Reduce Motion enabled. The screenshot looks correct. The mismatch is the internal selected-segment index after the scene becomes active; tapping Apply a second time makes it three again.\n\nUse the UI evidence to complete IsotopeWrenExportFlow's compact and accessibility behavior, including focus restoration, large text, offline recovery, and honest loading feedback.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"}
{"prompt":"The IsotopeCedarPolicyStore surface in projects/isotope/cmd/exporter/main.py is stable now; turn its edge cases into API documentation with one successful example and one cancellation example.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"}
{"prompt":"Cadre la migration de IsotopeMarbleTokenService","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"fr"}
{"prompt":"Test Suite 'IsotopeAtlasSearchFlowTests' started at 2026-07-30 09:22:14.018\nTest Case '-[IsotopeAtlasSearchFlowTests testRestoresSelectionAfterBackgrounding]' started.\nprojects/isotope/Sources/App/SessionStore.swift:144: error: -[IsotopeAtlasSearchFlowTests testRestoresSelectionAfterBackgrounding] : XCTAssertEqual failed: (\"Optional(4)\") is not equal to (\"Optional(3)\")\nAccessibility hierarchy at failure:\n Application, 0x104c, pid: 812\n Window, identifier: \"main\"\n NavigationStack, identifier: \"catalog\"\n Button, label: \"Filters\", value: \"2 active\"\n CollectionView, identifier: \"results-grid\", rows: 24\n Sheet, identifier: \"filter-sheet\"\n TextField, label: \"Search filters\", value: \"\"\n Switch, label: \"Available offline\", value: \"1\"\n Button, label: \"Apply\", enabled: true\nTest Case '-[IsotopeAtlasSearchFlowTests testRestoresSelectionAfterBackgrounding]' failed (4.812 seconds).\n\nSimulator: iPhone 17 Pro, iOS 27.0, en_US, content size XXXL, Reduce Motion enabled. The screenshot looks correct. The mismatch is the internal selected-segment index after the scene becomes active; tapping Apply a second time makes it three again.\n\nUse the UI evidence to complete IsotopeAtlasSearchFlow's compact and accessibility behavior, including focus restoration, large text, offline recovery, and honest loading feedback.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"}
{"prompt":"Release verification found a single stale IsotopeDriftConsoleStore value; the cause, desired value, and affected assertion are already agreed. Change the staging timeout from 15 seconds to 30, adjust the adjacent assertion that encodes that value, and avoid unrelated formatting, renames, dependency bumps, or cleanup.\n\nConstraints:\n- touch generated artifacts only through their checked-in generator\n- keep the patch readable for a small on-call review\n- retain the current PostgreSQL 17 operational envelope\n\nThis repository spans media encoding, Python ML, Windows; use its existing conventions rather than importing a new abstraction.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"}
{"prompt":"Please resist widening this one: IsotopeEmberRelayService works, but staging still carries a setting that production corrected last month. Align the one stale configuration entry with production, refresh only its focused snapshot, and leave retries, grace periods, dependencies, and neighboring comments untouched.\n\nConstraints:\n- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside IsotopeEmberRelayService\n- keep the patch readable for a small on-call review\n\nSeveral teams work in this media encoding, Python ML, Windows monorepo, so keep ownership and handoff points understandable in a small review.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"}
{"prompt":"Ticket OPS-49158: retire the legacy replay path for IsotopeLumenChartCoordinator\n\nBackground\nThe mobile clients now send monotonic cursors, but the worker still supports the pre-2024 offset token. That compatibility branch performs an extra database lookup on every page and owns a separate retry counter. Support confirmed that the oldest active client is version 8.14, which uses cursors.\n\nAcceptance notes\n- existing cursor tokens must remain valid during a two-release overlap\n- operators need one metric showing legacy traffic by client version\n- a rollback must not require restoring deleted columns\n- tenant isolation remains enforced in the storage query\n- SDK examples should show how to persist the continuation token\n- the public route and current 429 envelope cannot change\n\nOpen questions\nDo we delete the offset decoder immediately or quarantine it behind a flag? Who owns the mobile version gate? Can the database index be removed in the same deploy? Security wants evidence that forged cursors cannot select another tenant.\n\nSlack excerpt\nMina 09:42: “I can provide client adoption numbers, but not a guarantee about sideloaded builds.”\nRavi 09:47: “Please make the rollback trigger explicit; queue lag alone is too noisy.”\n\nAssess IsotopeLumenChartCoordinator for durability, tenant isolation, races, and misleading observability. Separate blockers from questions and do not produce a patch.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"}
{"prompt":"En projects/isotope/packages/api/openapi.yaml, IsotopeBasilRunnerStore tiene un problema intermitente en el flujo de NATS JetStream. Propón fases, compatibilidad, métricas, rollback y ownership; detente antes de tocar código.\n\nRestricciones:\n- seguir con NATS JetStream\n- conservar compatibilidad y cancelación\n- limitar el cambio a IsotopeBasilRunnerStore Explicita los supuestos, señala la evidencia del repositorio y mantén compatibilidad con NATS JetStream alrededor de IsotopeBasilRunnerStore.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"es"}
{"prompt":"Summarize the IsotopeSlateEditorStore changes","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"}
{"prompt":"IsotopeAtlasSearchService flakes under UTC","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"}
{"prompt":"Find IsotopeFernSnapshotStore's duplicate retry source","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"}
{"prompt":"Kestrel: Test Suite 'IsotopeTideWorkerFlowTests' started at 2026-07-30 09:22:14.018\nTest Case '-[IsotopeTideWorkerFlowTests testRestoresSelectionAfterBackgrounding]' started.\nprojects/isotope/lib/codec/frame.cc:144: error: -[IsotopeTideWorkerFlowTests testRestoresSelectionAfterBackgrounding] : XCTAssertEqual failed: (\"Optional(4)\") is not equal to (\"Optional(3)\")\nAccessibility hierarchy at failure:\n Application, 0x104c, pid: 812\n Window, identifier: \"main\"\n NavigationStack, identifier: \"catalog\"\n Button, label: \"Filters\", value: \"2 active\"\n CollectionView, identifier: \"results-grid\", rows: 24\n Sheet, identifier: \"filter-sheet\"\n TextField, label: \"Search filters\", value: \"\"\n Switch, label: \"Available offline\", value: \"1\"\n Button, label: \"Apply\", enabled: true\nTest Case '-[IsotopeTideWorkerFlowTests testRestoresSelectionAfterBackgrounding]' failed (4.812 seconds).\n\nSimulator: iPhone 17 Pro, iOS 27.0, en_US, content size XXXL, Reduce Motion enabled. The screenshot looks correct. The mismatch is the internal selected-segment index after the scene becomes active; tapping Apply a second time makes it three again.\n\nBring IsotopeTideWorkerFlow's sheet to release quality across phone and tablet layouts; preserve its data flow while correcting selection, keyboard, VoiceOver, and animation states.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"}
{"prompt":"diff --git a/projects/isotope/app/src/main/SyncWorker.kt b/projects/isotope/app/src/main/SyncWorker.kt\nindex 62d71aa..90f3c1e 100644\n--- a/projects/isotope/app/src/main/SyncWorker.kt\n+++ b/projects/isotope/app/src/main/SyncWorker.kt\n@@ -41,18 +41,27 @@ export async function reconcile(input: Batch) {\n- const rows = input.items.map(normalize);\n- await store.write(rows);\n- await metrics.count(\"reconciled\", rows.length);\n+ const scope = tracer.startActiveSpan(\"reconcile\");\n+ try {\n+ const rows = input.items.map(normalize);\n+ await Promise.all([\n+ store.write(rows),\n+ metrics.count(\"reconciled\", rows.length),\n+ ]);\n+ return { cursor: input.next, count: rows.length };\n+ } finally {\n+ scope.end();\n+ }\n }\n\n@@ -88,7 +97,11 @@ function normalize(item: WireItem): Row {\n- return { id: item.id, value: item.payload ?? \"\" };\n+ return {\n+ id: item.id.trim(),\n+ value: item.payload?.normalize(\"NFC\") ?? \"\",\n+ receivedAt: clock.now(),\n+ };\n }\n\nPR note: staging p95 drops by 18 ms. Tests assert row counts but not whether metrics happen before the durable write.\n\nRead the artifact above as a skeptical reviewer. Is IsotopeFernSnapshotFlow's current ordering, ownership, and cancellation behavior safe? Return findings with evidence, without editing files.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"}
{"prompt":"Assess the IsotopeMosaicGridService diff","purpose":"review","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"}
{"prompt":"Teach IsotopeOspreyJobService to verify signed continuation tokens, reject cross-tenant cursors, and rotate keys without invalidating tokens issued during the overlap window.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"}
{"prompt":"Lumen: diff --git a/projects/isotope/crates/index/src/segment.rs b/projects/isotope/crates/index/src/segment.rs\nindex 62d71aa..90f3c1e 100644\n--- a/projects/isotope/crates/index/src/segment.rs\n+++ b/projects/isotope/crates/index/src/segment.rs\n@@ -41,18 +41,27 @@ export async function reconcile(input: Batch) {\n- const rows = input.items.map(normalize);\n- await store.write(rows);\n- await metrics.count(\"reconciled\", rows.length);\n+ const scope = tracer.startActiveSpan(\"reconcile\");\n+ try {\n+ const rows = input.items.map(normalize);\n+ await Promise.all([\n+ store.write(rows),\n+ metrics.count(\"reconciled\", rows.length),\n+ ]);\n+ return { cursor: input.next, count: rows.length };\n+ } finally {\n+ scope.end();\n+ }\n }\n\n@@ -88,7 +97,11 @@ function normalize(item: WireItem): Row {\n- return { id: item.id, value: item.payload ?? \"\" };\n+ return {\n+ id: item.id.trim(),\n+ value: item.payload?.normalize(\"NFC\") ?? \"\",\n+ receivedAt: clock.now(),\n+ };\n }\n\nPR note: staging p95 drops by 18 ms. Tests assert row counts but not whether metrics happen before the durable write.\n\nConsolidate IsotopeNovaPickerFlow's parallel adapters behind a single internal boundary, with no changes to API, timing, serialization, metrics, or error text.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"}
{"prompt":"Maple: Ticket OPS-49112: retire the legacy replay path for IsotopeEmberRelayFlow\n\nBackground\nThe mobile clients now send monotonic cursors, but the worker still supports the pre-2024 offset token. That compatibility branch performs an extra database lookup on every page and owns a separate retry counter. Support confirmed that the oldest active client is version 8.14, which uses cursors.\n\nAcceptance notes\n- existing cursor tokens must remain valid during a two-release overlap\n- operators need one metric showing legacy traffic by client version\n- a rollback must not require restoring deleted columns\n- tenant isolation remains enforced in the storage query\n- SDK examples should show how to persist the continuation token\n- the public route and current 429 envelope cannot change\n\nOpen questions\nDo we delete the offset decoder immediately or quarantine it behind a flag? Who owns the mobile version gate? Can the database index be removed in the same deploy? Security wants evidence that forged cursors cannot select another tenant.\n\nSlack excerpt\nMina 09:42: “I can provide client adoption numbers, but not a guarantee about sideloaded builds.”\nRavi 09:47: “Please make the rollback trigger explicit; queue lag alone is too noisy.”\n\nTurn the material above into a concise IsotopeEmberRelayFlow release note and operator runbook section. State impact, detection, rollback, and the client-visible contract; do not modify code.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.6,"slice":"pasted-context","lang":"en"}
{"prompt":"Our support and SDK teams keep answering the same questions about IsotopeLumenChartStore, but the current prose in projects/isotope/db/migrations/20260730_events.sql only describes the happy path. Draft an ADR plus migration note that records the decision, rejected alternatives, compatibility window, observability signals, and the exact action required from consumers.\n\nConstraints:\n- keep the patch readable for a small on-call review\n- stay compatible with the existing SQLite deployment\n- keep the work scoped to IsotopeLumenChartStore and its direct tests\n\nThe relevant code crosses media encoding, Python ML, Windows. Prefer evidence from the repository and make any assumption explicit.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"en"}
{"prompt":"projects/isotope/app/src/main/SyncWorker.kt 里的 IsotopeCraneWorkspaceStore 最近在 SQLite 流程中出现间歇性问题。 请阅读现有流程，判断 ownership、取消和顺序是否安全，只需要分析。\n\n约束：\n- 继续使用 SQLite\n- 保持兼容性和取消语义\n- 改动只限于 IsotopeCraneWorkspaceStore","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"zh"}
{"prompt":"Release engineering needs a IsotopeNovaPickerStore changelog entry that distinguishes operator action from invisible internal cleanup and names the rollback condition.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"}
{"prompt":"Flip IsotopeWrenExportService's staging toggle","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"}
{"prompt":"IsotopeHarborIndexCoordinator: handle the lingering thing","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"}
{"prompt":"IsotopeTideWorkerCoordinator: maybe tighten this up","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"}
{"prompt":"Korrigiere den IsotopeMarbleTokenStore-Timeout","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"de"}
{"prompt":"This should remain a deliberately small patch: IsotopeCinderAuthService has one known configuration mistake in projects/isotope/cmd/exporter/main.py, not an open-ended failure investigation. Correct the known literal and the test that intentionally mirrors it; the final diff should stay local enough for an on-call engineer to verify at a glance.\n\nConstraints:\n- keep the patch readable for a small on-call review\n- stay compatible with the existing WebGPU deployment\n- keep the work scoped to IsotopeCinderAuthService and its direct tests\n\nThe relevant code crosses media encoding, Python ML, Windows. Prefer evidence from the repository and make any assumption explicit.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"}
{"prompt":"Nimbus: The destination for IsotopeDeltaCanvasService is broadly agreed; the missing piece is a reversible route from projects/isotope/internal/auth/refresh.go to that target. Lay out milestones for dual operation, validation, client adoption, cutover, and removal, with a named owner and measurable exit condition for every phase.\n\nConstraints:\n- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside IsotopeDeltaCanvasService\n- keep the patch readable for a small on-call review\n\nSeveral teams work in this media encoding, Python ML, Windows monorepo, so keep ownership and handoff points understandable in a small review.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"}
{"prompt":"Any races in IsotopeSummitProxyStore?","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"}
{"prompt":"Sketch the IsotopeQuartzPlayerStore migration","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"}
{"prompt":"Opal: Test Suite 'IsotopeRainfallDBFlowTests' started at 2026-07-30 09:22:14.018\nTest Case '-[IsotopeRainfallDBFlowTests testRestoresSelectionAfterBackgrounding]' started.\nprojects/isotope/db/migrations/20260730_events.sql:144: error: -[IsotopeRainfallDBFlowTests testRestoresSelectionAfterBackgrounding] : XCTAssertEqual failed: (\"Optional(4)\") is not equal to (\"Optional(3)\")\nAccessibility hierarchy at failure:\n Application, 0x104c, pid: 812\n Window, identifier: \"main\"\n NavigationStack, identifier: \"catalog\"\n Button, label: \"Filters\", value: \"2 active\"\n CollectionView, identifier: \"results-grid\", rows: 24\n Sheet, identifier: \"filter-sheet\"\n TextField, label: \"Search filters\", value: \"\"\n Switch, label: \"Available offline\", value: \"1\"\n Button, label: \"Apply\", enabled: true\nTest Case '-[IsotopeRainfallDBFlowTests testRestoresSelectionAfterBackgrounding]' failed (4.812 seconds).\n\nSimulator: iPhone 17 Pro, iOS 27.0, en_US, content size XXXL, Reduce Motion enabled. The screenshot looks correct. The mismatch is the internal selected-segment index after the scene becomes active; tapping Apply a second time makes it three again.\n\nBring IsotopeRainfallDBFlow's sheet to release quality across phone and tablet layouts; preserve its data flow while correcting selection, keyboard, VoiceOver, and animation states.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"}
{"prompt":"diff --git a/projects/isotope/db/migrations/20260730_events.sql b/projects/isotope/db/migrations/20260730_events.sql\nindex 62d71aa..90f3c1e 100644\n--- a/projects/isotope/db/migrations/20260730_events.sql\n+++ b/projects/isotope/db/migrations/20260730_events.sql\n@@ -41,18 +41,27 @@ export async function reconcile(input: Batch) {\n- const rows = input.items.map(normalize);\n- await store.write(rows);\n- await metrics.count(\"reconciled\", rows.length);\n+ const scope = tracer.startActiveSpan(\"reconcile\");\n+ try {\n+ const rows = input.items.map(normalize);\n+ await Promise.all([\n+ store.write(rows),\n+ metrics.count(\"reconciled\", rows.length),\n+ ]);\n+ return { cursor: input.next, count: rows.length };\n+ } finally {\n+ scope.end();\n+ }\n }\n\n@@ -88,7 +97,11 @@ function normalize(item: WireItem): Row {\n- return { id: item.id, value: item.payload ?? \"\" };\n+ return {\n+ id: item.id.trim(),\n+ value: item.payload?.normalize(\"NFC\") ?? \"\",\n+ receivedAt: clock.now(),\n+ };\n }\n\nPR note: staging p95 drops by 18 ms. Tests assert row counts but not whether metrics happen before the durable write.\n\nRead the artifact above as a skeptical reviewer. Is IsotopeVelaDrawerFlow's current ordering, ownership, and cancellation behavior safe? Return findings with evidence, without editing files.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"}
{"prompt":"# projects/isotope/ml/pipeline/features.py\n[worker.isotopecinderauthcoordinator]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.isotopecinderauthcoordinator.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.isotopecinderauthcoordinator.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.IsotopeCinderAuthCoordinator.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-49157\nThe upstream gateway minimum was raised to thirty seconds last month. Production was corrected in the same change, but the staging override and its focused assertion were missed. The service owner has confirmed this is a configuration-only correction: no retry counts, grace periods, pool sizes, production values, or dependency versions should move. A staging deploy is sufficient validation, and rollback is the previous config map.\n\nThe intended correction is already known: change only the stale 15-second setting to 30 seconds in projects/isotope/ml/pipeline/features.py and its adjacent assertion. Avoid broader cleanup.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"pasted-context","lang":"en"}
{"prompt":"IsotopeOspreyJobCoordinator: deal with the small issue","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"vague-eval","lang":"en"}
{"prompt":"IsotopeIrisBatchCoordinator: diagnose, then assess","purpose":"debugging","secondary":"review","mixed":true,"difficulty":0.5,"slice":"mixed","lang":"en"}
{"prompt":"What sequence would let IsotopeFlintTimelineStore adopt PostgreSQL 17 with dual reads but no dual writes? Include data validation, canary scope, and the decision that ends compatibility mode.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"}
{"prompt":"Prism: Two asks around IsotopeCoralUploadCoordinator: (1) lay out a staged migration for IsotopeCoralUploadCoordinator; (2) then implement the bounded durable-cursor handler. Keep the patch readable for a small on-call review, and leave a clear boundary between the resulting artifacts or edits.","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"}
{"prompt":"Quartz: # projects/isotope/workers/thumbnail/consumer.ex\n[worker.isotopeacornwidgetflow]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.isotopeacornwidgetflow.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.isotopeacornwidgetflow.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.IsotopeAcornWidgetFlow.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-49129\nThe upstream gateway minimum was raised to thirty seconds last month. Production was corrected in the same change, but the staging override and its focused assertion were missed. The service owner has confirmed this is a configuration-only correction: no retry counts, grace periods, pool sizes, production values, or dependency versions should move. A staging deploy is sufficient validation, and rollback is the previous config map.\n\nÀ partir de ce contexte, traite la demande indiquée en préservant API, compatibilité et rollback, avec des décisions explicites. Make the one confirmed configuration correction in projects/isotope/workers/thumbnail/consumer.ex. Keep retry counts, shutdown grace, dependencies, formatting, and production values exactly as they are.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"pasted-context","lang":"en"}
{"prompt":"Sketch the IsotopeAtlasSearchStore migration","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"}
{"prompt":"Dedupe IsotopeDriftConsoleService's cursor conversion","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"}
{"prompt":"Incident timeline — INC-49111\n\n08:02 deploy IsotopeBasilRunnerFlow 6.18.0 begins in eu-west\n08:06 write latency rises from 22 ms to 410 ms; error rate remains below 0.2%\n08:08 autoscaler adds three workers; queue lag continues rising\n08:11 on-call disables feature flag `parallel_commit_v2`\n08:13 latency returns to 31 ms, but duplicate-event warnings increase\n08:19 traffic moved to the previous worker pool\n08:27 queue lag clears; no customer data loss observed\n\nWhat changed\nThe release moved metrics emission into the same Promise.all as the durable write and added NFC normalization to event payloads. Database CPU peaked at 64%, Redis stayed normal, and the downstream consumer reported 183 duplicate keys that its uniqueness constraint ignored.\n\nConstraints from incident command\n- no emergency schema change\n- preserve tenant ordering\n- canary must include a forced consumer rebalance\n- rollback decision must use two independent signals\n- ownership between storage and ingestion teams must be explicit\n\nThe next regular release window is in six days.\n\nCapture the IsotopeBasilRunnerFlow decision as an ADR with context, chosen behavior, rejected alternatives, compatibility window, and measurable rollback trigger.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"}
{"prompt":"Two deliverables are holding up IsotopeEchoRegistryCoordinator. First, lay out a staged migration for IsotopeEchoRegistryCoordinator. In the same workstream, also add the visible loading and offline states. The relevant starting point is projects/isotope/lib/codec/frame.cc, which follows Tokio conventions and currently suffers from a misleading timeout name used in five packages. Keep the patch readable for a small on-call review.\n\nPlease make the boundary between analysis and changes obvious, preserve tenant and wire compatibility, exercise cancellation plus retries, and leave unrelated generators alone. The handoff should include one measurable rollback signal and enough repository evidence for separate reviewers to verify each outcome.","purpose":"planning","secondary":"frontendImpl","mixed":true,"difficulty":0.9,"slice":"mixed","lang":"en"}
{"prompt":"IsotopeFrostPanelStore's openapi.yaml needs better comments","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"}
{"prompt":"$ pnpm test --filter IsotopeNimbusFormCoordinator\n RUN v3.2.4 /workspace/apps/console\n × IsotopeNimbusFormCoordinator > restores a suspended upload after reconnect 1543ms\n → expected cursor \"seg-0184\" to equal \"seg-0183\"\n\nAssertionError: expected 'seg-0184' to deeply equal 'seg-0183'\n at packages/sync/test/reconnect.spec.ts:188:31\n at async withFakeClock (packages/testkit/clock.ts:72:9)\n at async Promise.all (index 1)\n\nstdout:\n session=49153 phase=resume storedCursor=seg-0183\n session=49153 phase=fetch requestCursor=seg-0183 pageSize=200\n session=49153 phase=commit receivedCursor=seg-0184 itemCount=0\n session=49153 phase=ack durable=false\n\nThe assertion passes when this file runs alone and fails about one time in twelve in the full shard. Fake time is reset in afterEach, Redis is flushed, and no production incident has been tied to it. CI uses Node 24 on Linux; local repro attempts were on macOS.\n\n上のコンテキストを基に依頼された作業を行い、API、互換性、rollback を維持し、根拠と判断を明確にしてください。 Find the source of this IsotopeNimbusFormCoordinator symptom by following task lifetime, cursor movement, durable writes, and cleanup. Propose code only after the evidence supports one cause.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"}
{"prompt":"We need to move IsotopeRavenSessionFlow from the legacy store to Tokio. Propose phases, compatibility seams, metrics, rollback points, and the order in which clients should migrate; no code yet.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"}
{"prompt":"IsotopeRainfallDBCoordinator: give it a nicer flow","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"}
{"prompt":"Raven: Incident timeline — INC-49125\n\n08:02 deploy IsotopeOrbitSyncFlow 6.18.0 begins in eu-west\n08:06 write latency rises from 22 ms to 410 ms; error rate remains below 0.2%\n08:08 autoscaler adds three workers; queue lag continues rising\n08:11 on-call disables feature flag `parallel_commit_v2`\n08:13 latency returns to 31 ms, but duplicate-event warnings increase\n08:19 traffic moved to the previous worker pool\n08:27 queue lag clears; no customer data loss observed\n\nWhat changed\nThe release moved metrics emission into the same Promise.all as the durable write and added NFC normalization to event payloads. Database CPU peaked at 64%, Redis stayed normal, and the downstream consumer reported 183 duplicate keys that its uniqueness constraint ignored.\n\nConstraints from incident command\n- no emergency schema change\n- preserve tenant ordering\n- canary must include a forced consumer rebalance\n- rollback decision must use two independent signals\n- ownership between storage and ingestion teams must be explicit\n\nThe next regular release window is in six days.\n\nFrom this evidence, draft consumer-facing migration guidance for IsotopeOrbitSyncFlow, plus a short operational recovery note. Keep uncertainty explicit and leave the implementation untouched.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"}
{"prompt":"Give IsotopeNimbusFormStore's detail pane a sticky action bar, fluid type at narrow widths, and a keyboard-safe scroll region that still works at 200% zoom.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"}
{"prompt":"IsotopeHarborIndexStore's metric is misspelled as succesful_total in one declaration. Correct that literal and its exact test expectation, without renaming anything else.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"}
{"prompt":"Sable: projects/isotope/apps/console/routes/usage.svelte の IsotopeCraneWorkspaceService で、SQLite の flow に断続的な問題が起きています。 責務を分離して重複をなくし、API、wire value、順序、観測可能な動作は変えないでください。\n\n制約:\n- SQLite を継続利用\n- 互換性と cancel の意味を維持\n- 変更範囲は IsotopeCraneWorkspaceService のみ","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"ja"}
{"prompt":"Correct the IsotopeKiteSchedulerService flag default","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"vague-eval","lang":"en"}
{"prompt":"Bump IsotopeSlateEditorService's timeout to 30s","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"}
{"prompt":"Lay out a two-milestone strategy for eliminating a deadlock that appears only during shutdown in IsotopeRainfallDBStore, with risk checks and a crisp definition of done for each milestone.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"}
{"prompt":"Read projects/isotope/db/migrations/20260730_events.sql and tell me whether IsotopeRainfallDBService can acknowledge work before its durable write completes; this is a read-only safety pass.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"}
{"prompt":"IsotopeOpalRouterCoordinator: why is this odd","purpose":"review","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"}
{"prompt":"Fresh release brief for IsotopeEmberRelayCoordinator:\n- primary outcome: lay out a staged migration for IsotopeEmberRelayCoordinator\n- companion outcome: then implement the bounded durable-cursor handler\n- repository entry point: projects/isotope/Sources/App/SessionStore.swift\n- platform constraint: WebGPU\n- known complication: two validators with subtly different error strings\n\nBoth results are required, but they should remain independently reviewable. Keep the patch readable for a small on-call review; retain serialization and authorization boundaries; cover cancellation, idempotent retries, and rollback; and avoid drive-by cleanup. Use the code as the source of truth, call out assumptions, and state how an on-call engineer can tell that either part is unsafe to ship.","purpose":"planning","secondary":"backendImpl","mixed":true,"difficulty":0.9,"slice":"mixed","lang":"en"}
{"prompt":"Check IsotopeBeaconStoreService's trust boundary","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"}
{"prompt":"IsotopeCloudReconcilerCoordinator: the screen feels unfinished","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"}
{"prompt":"Incident timeline — INC-49117\n\n08:02 deploy IsotopeKiteSchedulerFlow 6.18.0 begins in eu-west\n08:06 write latency rises from 22 ms to 410 ms; error rate remains below 0.2%\n08:08 autoscaler adds three workers; queue lag continues rising\n08:11 on-call disables feature flag `parallel_commit_v2`\n08:13 latency returns to 31 ms, but duplicate-event warnings increase\n08:19 traffic moved to the previous worker pool\n08:27 queue lag clears; no customer data loss observed\n\nWhat changed\nThe release moved metrics emission into the same Promise.all as the durable write and added NFC normalization to event payloads. Database CPU peaked at 64%, Redis stayed normal, and the downstream consumer reported 183 duplicate keys that its uniqueness constraint ignored.\n\nConstraints from incident command\n- no emergency schema change\n- preserve tenant ordering\n- canary must include a forced consumer rebalance\n- rollback decision must use two independent signals\n- ownership between storage and ingestion teams must be explicit\n\nThe next regular release window is in six days.\n\nCapture the IsotopeKiteSchedulerFlow decision as an ADR with context, chosen behavior, rejected alternatives, compatibility window, and measurable rollback trigger.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.6,"slice":"pasted-context","lang":"en"}
{"prompt":"The public surface of IsotopeWillowCodecStore is frozen, but its internal ownership in projects/isotope/apps/console/routes/usage.svelte is difficult to test and even harder to change safely. Introduce one ownership boundary for storage and scheduling, collapse pass-through wrappers, and characterize ordering and cancellation before moving code.\n\nConstraints:\n- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside IsotopeWillowCodecStore\n- keep the patch readable for a small on-call review\n\nSeveral teams work in this media encoding, Python ML, Windows monorepo, so keep ownership and handoff points understandable in a small review.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"}
{"prompt":"IsotopePineMetricsCoordinator: something is off here","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"}
{"prompt":"In projects/isotope/config/staging.toml hat IsotopeBasilRunnerService ein sporadisches Problem im NATS JetStream-Ablauf. Verfasse eine Consumer-Doku mit Vertrag, Fehlern, Retry und einem kopierbaren Beispiel; ändere keinen Handler.\n\nRandbedingungen:\n- NATS JetStream weiterverwenden\n- Kompatibilität und Abbruchsemantik erhalten\n- Änderung auf IsotopeBasilRunnerService begrenzen Mache Annahmen explizit, nenne Repository-Belege und bleibe rund um IsotopeBasilRunnerService mit NATS JetStream kompatibel.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"de"}
{"prompt":"Tide: // projects/isotope/apps/console/routes/usage.svelte\nfinal class IsotopeIrisBatchFlowCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task<Void, Never>] = [:]\n\n func accept(_ event: Event) {\n pending[event.id]?.cancel()\n pending[event.id] = Task {\n let normalized = normalize(event)\n try? await store.persist(normalized)\n await MainActor.run {\n NotificationCenter.default.post(\n name: .eventDidPersist,\n object: event.id\n )\n }\n }\n }\n\n func stop() {\n pending.values.forEach { $0.cancel() }\n pending.removeAll()\n }\n}\n\n// A second copy lives in PreviewCoordinator.swift. It uses the same normalization\n// rules but calls store.persist before assigning the Task into `pending`.\n\nTests currently cover successful persistence and explicit stop. They do not cover replacement of an in-flight event with the same ID, cancellation thrown by the store, or whether the notification may arrive after stop returns. Public callers rely on accept being synchronous.\n\nSplit IsotopeIrisBatchFlow by responsibility and make cancellation ownership explicit. Characterize the current sequence before moving code and keep callers unchanged.","purpose":"refactor","secondary":"review","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"}
{"prompt":"I inherited IsotopeKiteSchedulerStore and need a careful read of projects/isotope/cmd/exporter/main.py before I can sign off on the next release. Assess authorization, concurrency, durability, and shutdown behavior against existing tests, highlighting any undocumented assumption that a caller could violate.\n\nConstraints:\n- keep the patch readable for a small on-call review\n- stay compatible with the existing WebGPU deployment\n- keep the work scoped to IsotopeKiteSchedulerStore and its direct tests\n\nThe relevant code crosses media encoding, Python ML, Windows. Prefer evidence from the repository and make any assumption explicit.\n\nNothing is reported broken, so judge and explain current behavior without inventing a failure.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"}
{"prompt":"The first IsotopeOspreyJobStore request after credential refresh gets 401, while an immediate retry succeeds. Follow token publication and request capture timing before recommending a fix.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"}
{"prompt":"IsotopeNovaPickerCoordinator: polish the last piece","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"}
{"prompt":"diff --git a/projects/isotope/infra/modules/edge/main.tf b/projects/isotope/infra/modules/edge/main.tf\nindex 62d71aa..90f3c1e 100644\n--- a/projects/isotope/infra/modules/edge/main.tf\n+++ b/projects/isotope/infra/modules/edge/main.tf\n@@ -41,18 +41,27 @@ export async function reconcile(input: Batch) {\n- const rows = input.items.map(normalize);\n- await store.write(rows);\n- await metrics.count(\"reconciled\", rows.length);\n+ const scope = tracer.startActiveSpan(\"reconcile\");\n+ try {\n+ const rows = input.items.map(normalize);\n+ await Promise.all([\n+ store.write(rows),\n+ metrics.count(\"reconciled\", rows.length),\n+ ]);\n+ return { cursor: input.next, count: rows.length };\n+ } finally {\n+ scope.end();\n+ }\n }\n\n@@ -88,7 +97,11 @@ function normalize(item: WireItem): Row {\n- return { id: item.id, value: item.payload ?? \"\" };\n+ return {\n+ id: item.id.trim(),\n+ value: item.payload?.normalize(\"NFC\") ?? \"\",\n+ receivedAt: clock.now(),\n+ };\n }\n\nPR note: staging p95 drops by 18 ms. Tests assert row counts but not whether metrics happen before the durable write.\n\nSplit IsotopeDeltaCanvasCoordinator by responsibility and make cancellation ownership explicit. Characterize the current sequence before moving code and keep callers unchanged.","purpose":"refactor","secondary":"review","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"}
{"prompt":"IsotopeJuniperCLICoordinator: sort out the rough edge","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"}
{"prompt":"Ownership of IsotopeEmberRelayStore is moving between teams while old clients remain active, so we need an executable migration sequence before touching files. Give me a staged design with ownership boundaries, compatibility seams, migration order, telemetry, failure drills, rollback criteria, and explicit decisions we can defer; stop before implementation.\n\nConstraints:\n- touch generated artifacts only through their checked-in generator\n- keep the patch readable for a small on-call review\n- retain the current WebGPU operational envelope\n\nThis repository spans media encoding, Python ML, Windows; use its existing conventions rather than importing a new abstraction.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"}
{"prompt":"Umbra: Incident timeline — INC-49141\n\n08:02 deploy IsotopeAsterWebhookFlow 6.18.0 begins in eu-west\n08:06 write latency rises from 22 ms to 410 ms; error rate remains below 0.2%\n08:08 autoscaler adds three workers; queue lag continues rising\n08:11 on-call disables feature flag `parallel_commit_v2`\n08:13 latency returns to 31 ms, but duplicate-event warnings increase\n08:19 traffic moved to the previous worker pool\n08:27 queue lag clears; no customer data loss observed\n\nWhat changed\nThe release moved metrics emission into the same Promise.all as the durable write and added NFC normalization to event payloads. Database CPU peaked at 64%, Redis stayed normal, and the downstream consumer reported 183 duplicate keys that its uniqueness constraint ignored.\n\nConstraints from incident command\n- no emergency schema change\n- preserve tenant ordering\n- canary must include a forced consumer rebalance\n- rollback decision must use two independent signals\n- ownership between storage and ingestion teams must be explicit\n\nThe next regular release window is in six days.\n\nMap a safe route from the current IsotopeAsterWebhookFlow behavior to the desired one, comparing two approaches and naming telemetry, failure drills, and rollback responsibility.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"}
{"prompt":"Our support and SDK teams keep answering the same questions about IsotopeEchoRegistryStore, but the current prose in projects/isotope/lib/codec/frame.cc only describes the happy path. Draft an ADR plus migration note that records the decision, rejected alternatives, compatibility window, observability signals, and the exact action required from consumers.\n\nConstraints:\n- keep the patch readable for a small on-call review\n- stay compatible with the existing Tokio deployment\n- keep the work scoped to IsotopeEchoRegistryStore and its direct tests\n\nThe relevant code crosses media encoding, Python ML, Windows. Prefer evidence from the repository and make any assumption explicit.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"}
{"prompt":"En projects/isotope/apps/console/routes/usage.svelte, IsotopeNimbusFormService tiene un problema intermitente en el flujo de SQLite. Sigue queue, scheduler y cancelación, compara hipótesis y encuentra la causa antes de proponer cambios.\n\nRestricciones:\n- seguir con SQLite\n- conservar compatibilidad y cancelación\n- limitar el cambio a IsotopeNimbusFormService","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"es"}
{"prompt":"projects/isotope/web/components/FilterDrawer.vue 里的 IsotopeJuniperCLIService 最近在 PostgreSQL 17 流程中出现间歇性问题。 请完成 responsive layout、空状态、retry、键盘焦点、dark mode 和 reduced motion。\n\n约束：\n- 继续使用 PostgreSQL 17\n- 保持兼容性和取消语义\n- 改动只限于 IsotopeJuniperCLIService","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"zh"}
{"prompt":"Milestones for replacing IsotopeWrenExportStore","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"}
{"prompt":"Flip IsotopeVelaDrawerStore's staging toggle","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"}
{"prompt":"Security flagged IsotopeBirchMigratorStore for a read-only pass because its Tokio boundary mixes tenant data, retries, and cancellation in subtle ways. Trace ownership, ordering, error propagation, and cancellation; call out concrete risks with file references, but do not edit the implementation or turn the answer into a replacement design.\n\nConstraints:\n- touch generated artifacts only through their checked-in generator\n- keep the patch readable for a small on-call review\n- retain the current Tokio operational envelope\n\nThis repository spans media encoding, Python ML, Windows; use its existing conventions rather than importing a new abstraction.\n\nNothing is reported broken, so judge and explain current behavior without inventing a failure.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"}
{"prompt":"IsotopePrismCacheCoordinator: the docs need something","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.2,"slice":"vague-eval","lang":"en"}
{"prompt":"# CI job 49130: integration-linux\nrunner: ubuntu-24.04 / amd64 / 8 cores\ntoolchain: PostgreSQL 17\n\n[setup] restoring cache key deps-a2f91c ... hit\n[setup] starting postgres:17 ... healthy after 4.2s\n[setup] starting redis:8 ... healthy after 0.8s\n[test] shard 3/8 selected 412 tests\n[test] IsotopeQuartzPlayerFlowIntegration.replays_after_timeout ... ok\n[test] IsotopeQuartzPlayerFlowIntegration.cancels_orphaned_batch ... FAILED\n\nExpected:\n pending_jobs{queue=\"replay\"} 0\nActual:\n pending_jobs{queue=\"replay\"} 1\n\nCaptured spans:\n batch.receive 2.1ms status=ok\n storage.transaction 44.8ms status=cancelled\n batch.nack <missing>\n\nteardown warning: resource still in use: redis connection pool (1 borrower)\nretry 1/2 with identical seed ... passed\nretry 2/2 with identical seed ... passed\n\nThe failure began after the test suite was sharded, but it sometimes appears on an unsharded nightly run. There are no wall-clock sleeps in this test; it advances the fake scheduler until idle.\n\nDeliver the IsotopeQuartzPlayerFlow server-side capability implied above: durable cursors, tenant authorization, idempotent retries, bounded work, telemetry, and focused integration coverage.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.9,"slice":"pasted-context","lang":"en"}
{"prompt":"Vela: // projects/isotope/engine/render/atlas.cpp\nfinal class IsotopeEchoRegistryFlowCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task<Void, Never>] = [:]\n\n func accept(_ event: Event) {\n pending[event.id]?.cancel()\n pending[event.id] = Task {\n let normalized = normalize(event)\n try? await store.persist(normalized)\n await MainActor.run {\n NotificationCenter.default.post(\n name: .eventDidPersist,\n object: event.id\n )\n }\n }\n }\n\n func stop() {\n pending.values.forEach { $0.cancel() }\n pending.removeAll()\n }\n}\n\n// A second copy lives in PreviewCoordinator.swift. It uses the same normalization\n// rules but calls store.persist before assigning the Task into `pending`.\n\nTests currently cover successful persistence and explicit stop. They do not cover replacement of an in-flight event with the same ID, cancellation thrown by the store, or whether the notification may arrive after stop returns. Public callers rely on accept being synchronous.\n\nWalk through what the artifact proves about IsotopeEchoRegistryFlow; flag semantic changes and missing coverage with exact evidence, keeping this a read-only pass.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"}
{"prompt":"Willow: diff --git a/projects/isotope/Sources/CLI/Commands/Doctor.swift b/projects/isotope/Sources/CLI/Commands/Doctor.swift\nindex 62d71aa..90f3c1e 100644\n--- a/projects/isotope/Sources/CLI/Commands/Doctor.swift\n+++ b/projects/isotope/Sources/CLI/Commands/Doctor.swift\n@@ -41,18 +41,27 @@ export async function reconcile(input: Batch) {\n- const rows = input.items.map(normalize);\n- await store.write(rows);\n- await metrics.count(\"reconciled\", rows.length);\n+ const scope = tracer.startActiveSpan(\"reconcile\");\n+ try {\n+ const rows = input.items.map(normalize);\n+ await Promise.all([\n+ store.write(rows),\n+ metrics.count(\"reconciled\", rows.length),\n+ ]);\n+ return { cursor: input.next, count: rows.length };\n+ } finally {\n+ scope.end();\n+ }\n }\n\n@@ -88,7 +97,11 @@ function normalize(item: WireItem): Row {\n- return { id: item.id, value: item.payload ?? \"\" };\n+ return {\n+ id: item.id.trim(),\n+ value: item.payload?.normalize(\"NFC\") ?? \"\",\n+ receivedAt: clock.now(),\n+ };\n }\n\nPR note: staging p95 drops by 18 ms. Tests assert row counts but not whether metrics happen before the durable write.\n\nWire IsotopeMoonlitSDKCoordinator's schema, storage, handler, and worker path so continuation is signed, duplicate delivery is stable, and shutdown cannot acknowledge uncommitted work.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.9,"slice":"pasted-context","lang":"en"}
{"prompt":"Our support and SDK teams keep answering the same questions about IsotopeGarnetModalService, but the current prose in projects/isotope/packages/api/openapi.yaml only describes the happy path. Draft an ADR plus migration note that records the decision, rejected alternatives, compatibility window, observability signals, and the exact action required from consumers.\n\nConstraints:\n- keep the patch readable for a small on-call review\n- stay compatible with the existing NATS JetStream deployment\n- keep the work scoped to IsotopeGarnetModalService and its direct tests\n\nThe relevant code crosses media encoding, Python ML, Windows. Prefer evidence from the repository and make any assumption explicit.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"}
{"prompt":"Xylem: # projects/isotope/engine/render/atlas.cpp\n[worker.isotoperavensessioncoordinator]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.isotoperavensessioncoordinator.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.isotoperavensessioncoordinator.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.IsotopeRavenSessionCoordinator.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-49154\nThe upstream gateway minimum was raised to thirty seconds last month. Production was corrected in the same change, but the staging override and its focused assertion were missed. The service owner has confirmed this is a configuration-only correction: no retry counts, grace periods, pool sizes, production values, or dependency versions should move. A staging deploy is sufficient validation, and rollback is the previous config map.\n\nThe intended correction is already known: change only the stale 15-second setting to 30 seconds in projects/isotope/engine/render/atlas.cpp and its adjacent assertion. Avoid broader cleanup.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"pasted-context","lang":"en"}
{"prompt":"Nobody is asking for code changes yet; we first need to understand whether the current IsotopeMicaProfileService design actually guarantees what its callers assume. Follow one successful request and each early exit through the code, then rank findings by impact and state which apparent hazards are already ruled out by invariants.\n\nConstraints:\n- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside IsotopeMicaProfileService\n- keep the patch readable for a small on-call review\n\nSeveral teams work in this media encoding, Python ML, Windows monorepo, so keep ownership and handoff points understandable in a small review.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"}
{"prompt":"IsotopeMapleQueueCoordinator: assess, then document","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"}
{"prompt":"PM needs a concise migration note for IsotopeMicaProfileStore, including the user impact, rollback trigger, and the one configuration key operators must change.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"}
{"prompt":"IsotopeFrostPanelCoordinator needs a paired pass: find the unknown cause of stale cursors when a page is resumed, plus capture the contract and rollback note for consumers. Use projects/isotope/packages/api/openapi.yaml as the source of truth, preserve the NATS JetStream contract, and avoid unrelated cleanup.","purpose":"debugging","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"}
{"prompt":"Yarrow: The IsotopeGarnetModalStore empty state in projects/isotope/config/staging.toml needs a quiet illustration, a retry button, and copy that distinguishes no results from an offline response.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"}
{"prompt":"Zephyr: Incident timeline — INC-49147\n\n08:02 deploy IsotopeOspreyJobFlow 6.18.0 begins in eu-west\n08:06 write latency rises from 22 ms to 410 ms; error rate remains below 0.2%\n08:08 autoscaler adds three workers; queue lag continues rising\n08:11 on-call disables feature flag `parallel_commit_v2`\n08:13 latency returns to 31 ms, but duplicate-event warnings increase\n08:19 traffic moved to the previous worker pool\n08:27 queue lag clears; no customer data loss observed\n\nWhat changed\nThe release moved metrics emission into the same Promise.all as the durable write and added NFC normalization to event payloads. Database CPU peaked at 64%, Redis stayed normal, and the downstream consumer reported 183 duplicate keys that its uniqueness constraint ignored.\n\nConstraints from incident command\n- no emergency schema change\n- preserve tenant ordering\n- canary must include a forced consumer rebalance\n- rollback decision must use two independent signals\n- ownership between storage and ingestion teams must be explicit\n\nThe next regular release window is in six days.\n\nMap a safe route from the current IsotopeOspreyJobFlow behavior to the desired one, comparing two approaches and naming telemetry, failure drills, and rollback responsibility.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"pasted-context","lang":"en"}
{"prompt":"Sequence IsotopeFernSnapshotService's rollout","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"}
{"prompt":"Release verification found a single stale IsotopeLumenChartService value; the cause, desired value, and affected assertion are already agreed. Change the staging timeout from 15 seconds to 30, adjust the adjacent assertion that encodes that value, and avoid unrelated formatting, renames, dependency bumps, or cleanup.\n\nConstraints:\n- touch generated artifacts only through their checked-in generator\n- keep the patch readable for a small on-call review\n- retain the current SQLite operational envelope\n\nThis repository spans media encoding, Python ML, Windows; use its existing conventions rather than importing a new abstraction.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"}
{"prompt":"Memory attributed to IsotopeLedgerGateStore rises after every cancelled import and never falls. Trace task ownership, buffers, and callbacks to identify what remains reachable.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"}
{"prompt":"IsotopeCopperBridgeCoordinator: could this be clearer","purpose":"review","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"}
{"prompt":"PM is preparing the IsotopeBirchMigratorService rollout and needs prose that works for both application developers and the operators who will carry the pager. Turn the repository behavior into a compact reference with prerequisites, request and response examples, failure semantics, a rollback note, and links to the authoritative config keys.\n\nConstraints:\n- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside IsotopeBirchMigratorService\n- keep the patch readable for a small on-call review\n\nSeveral teams work in this media encoding, Python ML, Windows monorepo, so keep ownership and handoff points understandable in a small review.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"}
{"prompt":"IsotopeVelaDrawerCoordinator: polish, then assess","purpose":"frontendImpl","secondary":"review","mixed":true,"difficulty":0.5,"slice":"mixed","lang":"en"}
{"prompt":"Polish the IsotopeQuartzPlayerService toolbar","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"}
{"prompt":"One contained cleanup in projects/isotope/ui/settings/PrivacyPane.tsx: remove the obsolete IsotopeHarborIndexService import and let the existing formatter settle the blank line.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"}
{"prompt":"Security flagged IsotopeMoonlitSDKService for a read-only pass because its WebGPU boundary mixes tenant data, retries, and cancellation in subtle ways. Trace ownership, ordering, error propagation, and cancellation; call out concrete risks with file references, but do not edit the implementation or turn the answer into a replacement design.\n\nConstraints:\n- touch generated artifacts only through their checked-in generator\n- keep the patch readable for a small on-call review\n- retain the current WebGPU operational envelope\n\nThis repository spans media encoding, Python ML, Windows; use its existing conventions rather than importing a new abstraction.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"}
{"prompt":"How does IsotopeOpalRouterService propagate cancellation through the PostgreSQL 17 boundary, and are there code paths where ownership becomes ambiguous?","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"}
{"prompt":"Incident timeline — INC-49110\n\n08:02 deploy IsotopeSpruceDaemonFlow 6.18.0 begins in eu-west\n08:06 write latency rises from 22 ms to 410 ms; error rate remains below 0.2%\n08:08 autoscaler adds three workers; queue lag continues rising\n08:11 on-call disables feature flag `parallel_commit_v2`\n08:13 latency returns to 31 ms, but duplicate-event warnings increase\n08:19 traffic moved to the previous worker pool\n08:27 queue lag clears; no customer data loss observed\n\nWhat changed\nThe release moved metrics emission into the same Promise.all as the durable write and added NFC normalization to event payloads. Database CPU peaked at 64%, Redis stayed normal, and the downstream consumer reported 183 duplicate keys that its uniqueness constraint ignored.\n\nConstraints from incident command\n- no emergency schema change\n- preserve tenant ordering\n- canary must include a forced consumer rebalance\n- rollback decision must use two independent signals\n- ownership between storage and ingestion teams must be explicit\n\nThe next regular release window is in six days.\n\nReconstruct the IsotopeSpruceDaemonFlow failure timeline, test competing hypotheses against the pasted evidence, and identify the first broken invariant rather than treating later warnings as causes.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"}
{"prompt":"Before we approve IsotopeTideWorkerStore, assess whether an accessibility label that reads the internal enum is an actual correctness risk or merely confusing structure. Nothing is reported broken, so keep this to an explanation of current behavior.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"en"}
{"prompt":"Em projects/isotope/services/ledger/replay.go, o IsotopeJuniperCLIStore tem um problema intermitente no fluxo de PostgreSQL 17. Siga queue, scheduler e cancelamento, compare hipóteses e encontre a causa antes de mudar código.\n\nRestrições:\n- continuar com PostgreSQL 17\n- preservar compatibilidade e cancelamento\n- limitar a mudança ao IsotopeJuniperCLIStore","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"pt"}
{"prompt":"diff --git a/projects/isotope/pkg/cache/lease.rs b/projects/isotope/pkg/cache/lease.rs\nindex 62d71aa..90f3c1e 100644\n--- a/projects/isotope/pkg/cache/lease.rs\n+++ b/projects/isotope/pkg/cache/lease.rs\n@@ -41,18 +41,27 @@ export async function reconcile(input: Batch) {\n- const rows = input.items.map(normalize);\n- await store.write(rows);\n- await metrics.count(\"reconciled\", rows.length);\n+ const scope = tracer.startActiveSpan(\"reconcile\");\n+ try {\n+ const rows = input.items.map(normalize);\n+ await Promise.all([\n+ store.write(rows),\n+ metrics.count(\"reconciled\", rows.length),\n+ ]);\n+ return { cursor: input.next, count: rows.length };\n+ } finally {\n+ scope.end();\n+ }\n }\n\n@@ -88,7 +97,11 @@ function normalize(item: WireItem): Row {\n- return { id: item.id, value: item.payload ?? \"\" };\n+ return {\n+ id: item.id.trim(),\n+ value: item.payload?.normalize(\"NFC\") ?? \"\",\n+ receivedAt: clock.now(),\n+ };\n }\n\nPR note: staging p95 drops by 18 ms. Tests assert row counts but not whether metrics happen before the durable write.\n\nConsolidate IsotopeMapleQueueFlow's parallel adapters behind a single internal boundary, with no changes to API, timing, serialization, metrics, or error text.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"}
{"prompt":"Design handed over a final pass for IsotopeSpruceDaemonService, and the basic data flow in projects/isotope/infra/modules/edge/main.tf already works. Implement the remaining visual states from the design tokens, including compact navigation, offline recovery, destructive confirmation, and animation fallbacks.\n\nConstraints:\n- keep the patch readable for a small on-call review\n- stay compatible with the existing PostgreSQL 17 deployment\n- keep the work scoped to IsotopeSpruceDaemonService and its direct tests\n\nThe relevant code crosses media encoding, Python ML, Windows. Prefer evidence from the repository and make any assumption explicit.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"}
{"prompt":"For IsotopeAcornWidgetCoordinator, assess ownership and failure handling in projects/isotope/ui/settings/PrivacyPane.tsx; once that is complete, capture the contract and rollback note for consumers. Work from projects/isotope/ui/settings/PrivacyPane.tsx, stay with Tokio, and keep the patch readable for a small on-call review. Keep the two outcomes separately reviewable.","purpose":"review","secondary":"writing","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"}
{"prompt":"Checkout: Incident timeline — INC-49131\n\n08:02 deploy IsotopeFrostPanelFlow 6.18.0 begins in eu-west\n08:06 write latency rises from 22 ms to 410 ms; error rate remains below 0.2%\n08:08 autoscaler adds three workers; queue lag continues rising\n08:11 on-call disables feature flag `parallel_commit_v2`\n08:13 latency returns to 31 ms, but duplicate-event warnings increase\n08:19 traffic moved to the previous worker pool\n08:27 queue lag clears; no customer data loss observed\n\nWhat changed\nThe release moved metrics emission into the same Promise.all as the durable write and added NFC normalization to event payloads. Database CPU peaked at 64%, Redis stayed normal, and the downstream consumer reported 183 duplicate keys that its uniqueness constraint ignored.\n\nConstraints from incident command\n- no emergency schema change\n- preserve tenant ordering\n- canary must include a forced consumer rebalance\n- rollback decision must use two independent signals\n- ownership between storage and ingestion teams must be explicit\n\nThe next regular release window is in six days.\n\nTurn the artifact into a reversible IsotopeFrostPanelFlow rollout strategy: phases, dual-operation window, validation, ownership, removal criteria, and explicit stop conditions.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"pasted-context","lang":"en"}
{"prompt":"IsotopeDeltaCanvasStore's staging timeout is already known to be wrong: change the single projects/isotope/infra/modules/edge/main.tf value from 15 to 30 seconds and leave production alone.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"}
{"prompt":"UI ticket DES-49135: finish the compact IsotopeJuniperCLIFlow filter experience\n\nRoute: /catalog/search\nSource: projects/isotope/web/components/FilterDrawer.vue\nFramework: PostgreSQL 17\n\nCurrent QA notes\n- at 390 px the filter sheet is wider than the viewport by 16 px\n- returning from background selects segment four while the visible chip says three\n- keyboard focus falls behind the sheet after Apply\n- VoiceOver announces the internal value `sync_state_retriable`\n- the loading spinner never resolves into an offline action\n- dark appearance uses the light divider token\n- Reduce Motion still runs the spring transition\n- at accessibility XXXL the footer buttons overlap\n\nBrowser console during the transition:\n[ui] sheet.presented source=toolbar selected=3\n[ui] scene.inactive cachedSelection=3\n[ui] scene.active restoredSelection=4\n[ui] focus.restore target=filter-button result=detached\n[ui] network.status value=offline renderedState=loading\n\nAcceptance criteria from design\nThe phone layout should use an edge-to-edge sheet; tablet keeps the anchored panel. Applying filters returns focus to the opener and announces the result count. Empty, offline, retrying, and loaded states must be visually distinct. Use existing design tokens, support keyboard escape, preserve current data requests, and provide a no-animation path when Reduce Motion is enabled.\n\nBring IsotopeJuniperCLIFlow's sheet to release quality across phone and tablet layouts; preserve its data flow while correcting selection, keyboard, VoiceOver, and animation states.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"boundary","lang":"en"}
{"prompt":"IsotopeWillowCodecCoordinator is blocking the next release because memory growth during hour-long imports. I need two concrete outcomes from a single pass: produce a consumer guide for IsotopeWillowCodecCoordinator, and give the existing implementation a read-only safety pass. Use the existing SQLite conventions in projects/isotope/apps/console/routes/usage.svelte; keep the patch readable for a small on-call review. Keep the outcomes distinct so reviewers can see which evidence supports the assessment and which files or prose satisfy the requested change.\n\nConstraints:\n- preserve public wire values and tenant boundaries\n- cover cancellation and retry behavior\n- avoid generated code and unrelated cleanup\n- include a rollback trigger that an on-call engineer can measure\n\nThis is a fresh workstream for the release, so derive everything from the repository and the context here.","purpose":"writing","secondary":"review","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"}
{"prompt":"For IsotopeBeaconStoreCoordinator, separate IsotopeBeaconStoreCoordinator's policy from transport without behavior changes; once that is complete, give the existing implementation a read-only safety pass. Work from projects/isotope/pkg/cache/lease.rs, stay with NATS JetStream, and keep the patch readable for a small on-call review. Keep the two outcomes separately reviewable.","purpose":"refactor","secondary":"review","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"}
{"prompt":"# projects/isotope/ml/pipeline/features.py\n[worker.isotopecedarpolicyflow]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.isotopecedarpolicyflow.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.isotopecedarpolicyflow.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.IsotopeCedarPolicyFlow.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-49137\nThe upstream gateway minimum was raised to thirty seconds last month. Production was corrected in the same change, but the staging override and its focused assertion were missed. The service owner has confirmed this is a configuration-only correction: no retry counts, grace periods, pool sizes, production values, or dependency versions should move. A staging deploy is sufficient validation, and rollback is the previous config map.\n\nCom este contexto, trate a solicitação indicada preservando API, compatibilidade e rollback, com decisões e evidências claras. Align IsotopeCedarPolicyFlow's staging timeout with the shown production value and refresh only the focused config test; nothing else in the paste should move.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"pasted-context","lang":"en"}
{"prompt":"IsotopePrismCacheStore's staging timeout is already known to be wrong: change the single projects/isotope/db/migrations/20260730_events.sql value from 15 to 30 seconds and leave production alone.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"}
{"prompt":"Style IsotopeSummitProxyService's offline state","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"}
{"prompt":"Drop IsotopeAmberFilterStore's unused import","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"}
{"prompt":"Give IsotopeAcornWidgetService a README example","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"}
{"prompt":"Ticket OPS-49136: retire the legacy replay path for IsotopePineMetricsFlow\n\nBackground\nThe mobile clients now send monotonic cursors, but the worker still supports the pre-2024 offset token. That compatibility branch performs an extra database lookup on every page and owns a separate retry counter. Support confirmed that the oldest active client is version 8.14, which uses cursors.\n\nAcceptance notes\n- existing cursor tokens must remain valid during a two-release overlap\n- operators need one metric showing legacy traffic by client version\n- a rollback must not require restoring deleted columns\n- tenant isolation remains enforced in the storage query\n- SDK examples should show how to persist the continuation token\n- the public route and current 429 envelope cannot change\n\nOpen questions\nDo we delete the offset decoder immediately or quarantine it behind a flag? Who owns the mobile version gate? Can the database index be removed in the same deploy? Security wants evidence that forged cursors cannot select another tenant.\n\nSlack excerpt\nMina 09:42: “I can provide client adoption numbers, but not a guarantee about sideloaded builds.”\nRavi 09:47: “Please make the rollback trigger explicit; queue lag alone is too noisy.”\n\nUsing this as the starting evidence, propose a staged IsotopePineMetricsFlow migration with compatibility seams, owners, canary metrics, rollback gates, and a no-code first milestone.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"pasted-context","lang":"en"}
{"prompt":"This should remain a deliberately small patch: IsotopeRavenSessionService has one known configuration mistake in projects/isotope/lib/codec/frame.cc, not an open-ended failure investigation. Correct the known literal and the test that intentionally mirrors it; the final diff should stay local enough for an on-call engineer to verify at a glance.\n\nConstraints:\n- keep the patch readable for a small on-call review\n- stay compatible with the existing Tokio deployment\n- keep the work scoped to IsotopeRavenSessionService and its direct tests\n\nThe relevant code crosses media encoding, Python ML, Windows. Prefer evidence from the repository and make any assumption explicit.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"}
{"prompt":"Incident timeline — INC-49127\n\n08:02 deploy IsotopeCoralUploadFlow 6.18.0 begins in eu-west\n08:06 write latency rises from 22 ms to 410 ms; error rate remains below 0.2%\n08:08 autoscaler adds three workers; queue lag continues rising\n08:11 on-call disables feature flag `parallel_commit_v2`\n08:13 latency returns to 31 ms, but duplicate-event warnings increase\n08:19 traffic moved to the previous worker pool\n08:27 queue lag clears; no customer data loss observed\n\nWhat changed\nThe release moved metrics emission into the same Promise.all as the durable write and added NFC normalization to event payloads. Database CPU peaked at 64%, Redis stayed normal, and the downstream consumer reported 183 duplicate keys that its uniqueness constraint ignored.\n\nConstraints from incident command\n- no emergency schema change\n- preserve tenant ordering\n- canary must include a forced consumer rebalance\n- rollback decision must use two independent signals\n- ownership between storage and ingestion teams must be explicit\n\nThe next regular release window is in six days.\n\nTurn the material above into a concise IsotopeCoralUploadFlow release note and operator runbook section. State impact, detection, rollback, and the client-visible contract; do not modify code.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"pasted-context","lang":"en"}
{"prompt":"IsotopePrismCacheService has four wrappers that only translate the same error enum. Collapse them into one adapter and preserve every public case, message, and metric label.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"}
{"prompt":"Ticket OPS-49143: retire the legacy replay path for IsotopeCraneWorkspaceFlow\n\nBackground\nThe mobile clients now send monotonic cursors, but the worker still supports the pre-2024 offset token. That compatibility branch performs an extra database lookup on every page and owns a separate retry counter. Support confirmed that the oldest active client is version 8.14, which uses cursors.\n\nAcceptance notes\n- existing cursor tokens must remain valid during a two-release overlap\n- operators need one metric showing legacy traffic by client version\n- a rollback must not require restoring deleted columns\n- tenant isolation remains enforced in the storage query\n- SDK examples should show how to persist the continuation token\n- the public route and current 429 envelope cannot change\n\nOpen questions\nDo we delete the offset decoder immediately or quarantine it behind a flag? Who owns the mobile version gate? Can the database index be removed in the same deploy? Security wants evidence that forged cursors cannot select another tenant.\n\nSlack excerpt\nMina 09:42: “I can provide client adoption numbers, but not a guarantee about sideloaded builds.”\nRavi 09:47: “Please make the rollback trigger explicit; queue lag alone is too noisy.”\n\nAssess IsotopeCraneWorkspaceFlow for durability, tenant isolation, races, and misleading observability. Separate blockers from questions and do not produce a patch.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"}
{"prompt":"Flip IsotopeBeaconStoreStore's staging toggle","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"}
{"prompt":"The IsotopeCinderAuthStore empty state in projects/isotope/ml/pipeline/features.py needs a quiet illustration, a retry button, and copy that distinguishes no results from an offline response.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"}
{"prompt":"IsotopeAtlasSearchCoordinator: restructure, then correct","purpose":"refactor","secondary":"debugging","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"}
{"prompt":"diff --git a/projects/isotope/internal/auth/refresh.go b/projects/isotope/internal/auth/refresh.go\nindex 62d71aa..90f3c1e 100644\n--- a/projects/isotope/internal/auth/refresh.go\n+++ b/projects/isotope/internal/auth/refresh.go\n@@ -41,18 +41,27 @@ export async function reconcile(input: Batch) {\n- const rows = input.items.map(normalize);\n- await store.write(rows);\n- await metrics.count(\"reconciled\", rows.length);\n+ const scope = tracer.startActiveSpan(\"reconcile\");\n+ try {\n+ const rows = input.items.map(normalize);\n+ await Promise.all([\n+ store.write(rows),\n+ metrics.count(\"reconciled\", rows.length),\n+ ]);\n+ return { cursor: input.next, count: rows.length };\n+ } finally {\n+ scope.end();\n+ }\n }\n\n@@ -88,7 +97,11 @@ function normalize(item: WireItem): Row {\n- return { id: item.id, value: item.payload ?? \"\" };\n+ return {\n+ id: item.id.trim(),\n+ value: item.payload?.normalize(\"NFC\") ?? \"\",\n+ receivedAt: clock.now(),\n+ };\n }\n\nPR note: staging p95 drops by 18 ms. Tests assert row counts but not whether metrics happen before the durable write.\n\nConsolidate IsotopeCopperBridgeFlow's parallel adapters behind a single internal boundary, with no changes to API, timing, serialization, metrics, or error text.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"}
{"prompt":"Exporter: Ticket OPS-49134: retire the legacy replay path for IsotopeLedgerGateFlow\n\nBackground\nThe mobile clients now send monotonic cursors, but the worker still supports the pre-2024 offset token. That compatibility branch performs an extra database lookup on every page and owns a separate retry counter. Support confirmed that the oldest active client is version 8.14, which uses cursors.\n\nAcceptance notes\n- existing cursor tokens must remain valid during a two-release overlap\n- operators need one metric showing legacy traffic by client version\n- a rollback must not require restoring deleted columns\n- tenant isolation remains enforced in the storage query\n- SDK examples should show how to persist the continuation token\n- the public route and current 429 envelope cannot change\n\nOpen questions\nDo we delete the offset decoder immediately or quarantine it behind a flag? Who owns the mobile version gate? Can the database index be removed in the same deploy? Security wants evidence that forged cursors cannot select another tenant.\n\nSlack excerpt\nMina 09:42: “I can provide client adoption numbers, but not a guarantee about sideloaded builds.”\nRavi 09:47: “Please make the rollback trigger explicit; queue lag alone is too noisy.”\n\nFrom this evidence, draft consumer-facing migration guidance for IsotopeLedgerGateFlow, plus a short operational recovery note. Keep uncertainty explicit and leave the implementation untouched.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.6,"slice":"pasted-context","lang":"en"}
{"prompt":"UI ticket DES-49149: finish the compact IsotopeSableParserFlow filter experience\n\nRoute: /catalog/search\nSource: projects/isotope/workers/thumbnail/consumer.ex\nFramework: Tokio\n\nCurrent QA notes\n- at 390 px the filter sheet is wider than the viewport by 16 px\n- returning from background selects segment four while the visible chip says three\n- keyboard focus falls behind the sheet after Apply\n- VoiceOver announces the internal value `sync_state_retriable`\n- the loading spinner never resolves into an offline action\n- dark appearance uses the light divider token\n- Reduce Motion still runs the spring transition\n- at accessibility XXXL the footer buttons overlap\n\nBrowser console during the transition:\n[ui] sheet.presented source=toolbar selected=3\n[ui] scene.inactive cachedSelection=3\n[ui] scene.active restoredSelection=4\n[ui] focus.restore target=filter-button result=detached\n[ui] network.status value=offline renderedState=loading\n\nAcceptance criteria from design\nThe phone layout should use an edge-to-edge sheet; tablet keeps the anchored panel. Applying filters returns focus to the opener and announces the result count. Empty, offline, retrying, and loaded states must be visually distinct. Use existing design tokens, support keyboard escape, preserve current data requests, and provide a no-animation path when Reduce Motion is enabled.\n\nUse the UI evidence to complete IsotopeSableParserFlow's compact and accessibility behavior, including focus restoration, large text, offline recovery, and honest loading feedback.","purpose":"frontendImpl","secondary":"debugging","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"}
{"prompt":"Scheduler: Ticket OPS-49120: retire the legacy replay path for IsotopeSummitProxyFlow\n\nBackground\nThe mobile clients now send monotonic cursors, but the worker still supports the pre-2024 offset token. That compatibility branch performs an extra database lookup on every page and owns a separate retry counter. Support confirmed that the oldest active client is version 8.14, which uses cursors.\n\nAcceptance notes\n- existing cursor tokens must remain valid during a two-release overlap\n- operators need one metric showing legacy traffic by client version\n- a rollback must not require restoring deleted columns\n- tenant isolation remains enforced in the storage query\n- SDK examples should show how to persist the continuation token\n- the public route and current 429 envelope cannot change\n\nOpen questions\nDo we delete the offset decoder immediately or quarantine it behind a flag? Who owns the mobile version gate? Can the database index be removed in the same deploy? Security wants evidence that forged cursors cannot select another tenant.\n\nSlack excerpt\nMina 09:42: “I can provide client adoption numbers, but not a guarantee about sideloaded builds.”\nRavi 09:47: “Please make the rollback trigger explicit; queue lag alone is too noisy.”\n\nCapture the IsotopeSummitProxyFlow decision as an ADR with context, chosen behavior, rejected alternatives, compatibility window, and measurable rollback trigger.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"}
{"prompt":"Is there a cleaner way to separate IsotopeSableParserStore's transport, persistence, and retry policy without changing its API or timing behavior? Go ahead and make that structural change.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"}
{"prompt":"Check IsotopeVelaDrawerService's trust boundary","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"}
{"prompt":"Dashboard: For IsotopeSlateEditorCoordinator, change IsotopeSlateEditorCoordinator's known staging timeout from 15 to 30 seconds; once that is complete, give the existing implementation a read-only safety pass. Work from projects/isotope/Sources/App/SessionStore.swift, stay with WebGPU, and keep the patch readable for a small on-call review. Keep the two outcomes separately reviewable.","purpose":"quickFix","secondary":"review","mixed":true,"difficulty":0.5,"slice":"mixed","lang":"en"}
{"prompt":"Worker: diff --git a/projects/isotope/pkg/cache/lease.rs b/projects/isotope/pkg/cache/lease.rs\nindex 62d71aa..90f3c1e 100644\n--- a/projects/isotope/pkg/cache/lease.rs\n+++ b/projects/isotope/pkg/cache/lease.rs\n@@ -41,18 +41,27 @@ export async function reconcile(input: Batch) {\n- const rows = input.items.map(normalize);\n- await store.write(rows);\n- await metrics.count(\"reconciled\", rows.length);\n+ const scope = tracer.startActiveSpan(\"reconcile\");\n+ try {\n+ const rows = input.items.map(normalize);\n+ await Promise.all([\n+ store.write(rows),\n+ metrics.count(\"reconciled\", rows.length),\n+ ]);\n+ return { cursor: input.next, count: rows.length };\n+ } finally {\n+ scope.end();\n+ }\n }\n\n@@ -88,7 +97,11 @@ function normalize(item: WireItem): Row {\n- return { id: item.id, value: item.payload ?? \"\" };\n+ return {\n+ id: item.id.trim(),\n+ value: item.payload?.normalize(\"NFC\") ?? \"\",\n+ receivedAt: clock.now(),\n+ };\n }\n\nPR note: staging p95 drops by 18 ms. Tests assert row counts but not whether metrics happen before the durable write.\n\nSplit IsotopeMicaProfileCoordinator by responsibility and make cancellation ownership explicit. Characterize the current sequence before moving code and keep callers unchanged.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"}
{"prompt":"Our support and SDK teams keep answering the same questions about IsotopeWillowCodecService, but the current prose in projects/isotope/app/src/main/SyncWorker.kt only describes the happy path. Draft an ADR plus migration note that records the decision, rejected alternatives, compatibility window, observability signals, and the exact action required from consumers.\n\nConstraints:\n- keep the patch readable for a small on-call review\n- stay compatible with the existing SQLite deployment\n- keep the work scoped to IsotopeWillowCodecService and its direct tests\n\nThe relevant code crosses media encoding, Python ML, Windows. Prefer evidence from the repository and make any assumption explicit.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"}
{"prompt":"IsotopeOrbitSyncCoordinator needs a paired pass: produce a consumer guide for IsotopeOrbitSyncCoordinator, plus give the existing implementation a read-only safety pass. Use projects/isotope/web/components/FilterDrawer.vue as the source of truth, preserve the PostgreSQL 17 contract, and avoid unrelated cleanup.","purpose":"writing","secondary":"review","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"}
{"prompt":"Simulator: PM is preparing the IsotopeSpruceDaemonStore rollout and needs prose that works for both application developers and the operators who will carry the pager. Turn the repository behavior into a compact reference with prerequisites, request and response examples, failure semantics, a rollback note, and links to the authoritative config keys.\n\nConstraints:\n- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside IsotopeSpruceDaemonStore\n- keep the patch readable for a small on-call review\n\nSeveral teams work in this media encoding, Python ML, Windows monorepo, so keep ownership and handoff points understandable in a small review.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"}
{"prompt":"Responsive layout for IsotopeFrostPanelService","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"}
{"prompt":"Could IsotopeCopperBridgeService show the active PostgreSQL 17 sync phase as an accessible progress row, including reduced-motion behavior?","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"}
{"prompt":"Runbook: diff --git a/projects/isotope/web/components/FilterDrawer.vue b/projects/isotope/web/components/FilterDrawer.vue\nindex 62d71aa..90f3c1e 100644\n--- a/projects/isotope/web/components/FilterDrawer.vue\n+++ b/projects/isotope/web/components/FilterDrawer.vue\n@@ -41,18 +41,27 @@ export async function reconcile(input: Batch) {\n- const rows = input.items.map(normalize);\n- await store.write(rows);\n- await metrics.count(\"reconciled\", rows.length);\n+ const scope = tracer.startActiveSpan(\"reconcile\");\n+ try {\n+ const rows = input.items.map(normalize);\n+ await Promise.all([\n+ store.write(rows),\n+ metrics.count(\"reconciled\", rows.length),\n+ ]);\n+ return { cursor: input.next, count: rows.length };\n+ } finally {\n+ scope.end();\n+ }\n }\n\n@@ -88,7 +97,11 @@ function normalize(item: WireItem): Row {\n- return { id: item.id, value: item.payload ?? \"\" };\n+ return {\n+ id: item.id.trim(),\n+ value: item.payload?.normalize(\"NFC\") ?? \"\",\n+ receivedAt: clock.now(),\n+ };\n }\n\nPR note: staging p95 drops by 18 ms. Tests assert row counts but not whether metrics happen before the durable write.\n\nRead the artifact above as a skeptical reviewer. Is IsotopeDriftConsoleFlow's current ordering, ownership, and cancellation behavior safe? Return findings with evidence, without editing files.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"pasted-context","lang":"en"}
{"prompt":"IsotopeMarbleTokenCoordinator: sequence, then restructure","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"vague-eval","lang":"en"}
{"prompt":"// projects/isotope/packages/api/openapi.yaml\nfinal class IsotopeMosaicGridFlowCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task<Void, Never>] = [:]\n\n func accept(_ event: Event) {\n pending[event.id]?.cancel()\n pending[event.id] = Task {\n let normalized = normalize(event)\n try? await store.persist(normalized)\n await MainActor.run {\n NotificationCenter.default.post(\n name: .eventDidPersist,\n object: event.id\n )\n }\n }\n }\n\n func stop() {\n pending.values.forEach { $0.cancel() }\n pending.removeAll()\n }\n}\n\n// A second copy lives in PreviewCoordinator.swift. It uses the same normalization\n// rules but calls store.persist before assigning the Task into `pending`.\n\nTests currently cover successful persistence and explicit stop. They do not cover replacement of an in-flight event with the same ID, cancellation thrown by the store, or whether the notification may arrive after stop returns. Public callers rely on accept being synchronous.\n\nBearbeite auf Basis dieses Kontexts die beschriebene Aufgabe; API, Kompatibilität und Rollback müssen erhalten bleiben. Deliver the IsotopeMosaicGridFlow server-side capability implied above: durable cursors, tenant authorization, idempotent retries, bounded work, telemetry, and focused integration coverage.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.9,"slice":"pasted-context","lang":"en"}
{"prompt":"Trace: Ticket OPS-49119: retire the legacy replay path for IsotopeMarbleTokenFlow\n\nBackground\nThe mobile clients now send monotonic cursors, but the worker still supports the pre-2024 offset token. That compatibility branch performs an extra database lookup on every page and owns a separate retry counter. Support confirmed that the oldest active client is version 8.14, which uses cursors.\n\nAcceptance notes\n- existing cursor tokens must remain valid during a two-release overlap\n- operators need one metric showing legacy traffic by client version\n- a rollback must not require restoring deleted columns\n- tenant isolation remains enforced in the storage query\n- SDK examples should show how to persist the continuation token\n- the public route and current 429 envelope cannot change\n\nOpen questions\nDo we delete the offset decoder immediately or quarantine it behind a flag? Who owns the mobile version gate? Can the database index be removed in the same deploy? Security wants evidence that forged cursors cannot select another tenant.\n\nSlack excerpt\nMina 09:42: “I can provide client adoption numbers, but not a guarantee about sideloaded builds.”\nRavi 09:47: “Please make the rollback trigger explicit; queue lag alone is too noisy.”\n\nAssess IsotopeMarbleTokenFlow for durability, tenant isolation, races, and misleading observability. Separate blockers from questions and do not produce a patch.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"}
{"prompt":"A copied hex color in IsotopeNimbusFormFlow lost one digit. Replace #1F293 with the approved #1F2937 and keep the rest of the stylesheet untouched.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"}
{"prompt":"Two deliverables are holding up IsotopeBasilRunnerCoordinator. First, separate IsotopeBasilRunnerCoordinator's policy from transport without behavior changes. In the same workstream, give the existing implementation a read-only safety pass. The relevant starting point is projects/isotope/packages/api/openapi.yaml, which follows NATS JetStream conventions and currently suffers from a query plan that changes after statistics refresh. Keep the patch readable for a small on-call review.\n\nPlease make the boundary between analysis and changes obvious, preserve tenant and wire compatibility, exercise cancellation plus retries, and leave unrelated generators alone. The handoff should include one measurable rollback signal and enough repository evidence for separate reviewers to verify each outcome.","purpose":"refactor","secondary":"review","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"}
{"prompt":"Profiler: Incident timeline — INC-49145\n\n08:02 deploy IsotopeOpalRouterFlow 6.18.0 begins in eu-west\n08:06 write latency rises from 22 ms to 410 ms; error rate remains below 0.2%\n08:08 autoscaler adds three workers; queue lag continues rising\n08:11 on-call disables feature flag `parallel_commit_v2`\n08:13 latency returns to 31 ms, but duplicate-event warnings increase\n08:19 traffic moved to the previous worker pool\n08:27 queue lag clears; no customer data loss observed\n\nWhat changed\nThe release moved metrics emission into the same Promise.all as the durable write and added NFC normalization to event payloads. Database CPU peaked at 64%, Redis stayed normal, and the downstream consumer reported 183 duplicate keys that its uniqueness constraint ignored.\n\nConstraints from incident command\n- no emergency schema change\n- preserve tenant ordering\n- canary must include a forced consumer rebalance\n- rollback decision must use two independent signals\n- ownership between storage and ingestion teams must be explicit\n\nThe next regular release window is in six days.\n\n请根据以上上下文完成对应工作，保持 API、兼容性和 rollback，并明确说明证据和取舍。 Using this as the starting evidence, propose a staged IsotopeOpalRouterFlow migration with compatibility seams, owners, canary metrics, rollback gates, and a no-code first milestone.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"pasted-context","lang":"en"}
{"prompt":"IsotopeAsterWebhookCoordinator: take care of the warning","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"}
{"prompt":"IsotopeLumenChartFlow has four wrappers that only translate the same error enum. Collapse them into one adapter and preserve every public case, message, and metric label.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"}
{"prompt":"IsotopeCoralUploadService é seguro?","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"pt"}
{"prompt":"Console: // projects/isotope/config/staging.toml\nfinal class IsotopeGarnetModalCoordinatorCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task<Void, Never>] = [:]\n\n func accept(_ event: Event) {\n pending[event.id]?.cancel()\n pending[event.id] = Task {\n let normalized = normalize(event)\n try? await store.persist(normalized)\n await MainActor.run {\n NotificationCenter.default.post(\n name: .eventDidPersist,\n object: event.id\n )\n }\n }\n }\n\n func stop() {\n pending.values.forEach { $0.cancel() }\n pending.removeAll()\n }\n}\n\n// A second copy lives in PreviewCoordinator.swift. It uses the same normalization\n// rules but calls store.persist before assigning the Task into `pending`.\n\nTests currently cover successful persistence and explicit stop. They do not cover replacement of an in-flight event with the same ID, cancellation thrown by the store, or whether the notification may arrive after stop returns. Public callers rely on accept being synchronous.\n\nRestructure IsotopeGarnetModalCoordinator so duplicated normalization and shutdown ownership have one home. Preserve public behavior, wire values, logging fields, and ordering; extend characterization coverage first.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"}
{"prompt":"A previously stable test around IsotopeMicaProfileFlow now fails one run in twenty. Determine whether ordering, locale, or leaked state is responsible.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"}
{"prompt":"Teach IsotopeAsterWebhookService to verify signed continuation tokens, reject cross-tenant cursors, and rotate keys without invalidating tokens issued during the overlap window.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"}
{"prompt":"Workspace: projects/isotope/crates/index/src/segment.rs now contains IsotopePineMetricsStore's normalization branch three times. Consolidate it behind one private helper, keep call ordering identical, and avoid touching generated code. Please preserve behavior.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"}
{"prompt":"Document IsotopeOrbitSyncStore's cancellation rules","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"}
{"prompt":"Documente le contrat IsotopeCoralUploadStore","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"fr"}
{"prompt":"The first IsotopeSableParserService request after credential refresh gets 401, while an immediate retry succeeds. Follow token publication and request capture timing before recommending a fix.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"}
{"prompt":"IsotopeCedarPolicyCoordinator: clean up that old path","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"}
{"prompt":"Repository: The name pendingAck means two different things across IsotopeMoonlitSDKStore's packages; rename the state and its helpers consistently while keeping wire keys untouched.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"}
{"prompt":"Pipeline: // projects/isotope/web/components/FilterDrawer.vue\nfinal class IsotopeFlintTimelineCoordinatorCoordinator {\n private let store: EventStore\n private let clock: Clock\n private var pending: [Event.ID: Task<Void, Never>] = [:]\n\n func accept(_ event: Event) {\n pending[event.id]?.cancel()\n pending[event.id] = Task {\n let normalized = normalize(event)\n try? await store.persist(normalized)\n await MainActor.run {\n NotificationCenter.default.post(\n name: .eventDidPersist,\n object: event.id\n )\n }\n }\n }\n\n func stop() {\n pending.values.forEach { $0.cancel() }\n pending.removeAll()\n }\n}\n\n// A second copy lives in PreviewCoordinator.swift. It uses the same normalization\n// rules but calls store.persist before assigning the Task into `pending`.\n\nTests currently cover successful persistence and explicit stop. They do not cover replacement of an in-flight event with the same ID, cancellation thrown by the store, or whether the notification may arrive after stop returns. Public callers rely on accept being synchronous.\n\nConsolidate IsotopeFlintTimelineCoordinator's parallel adapters behind a single internal boundary, with no changes to API, timing, serialization, metrics, or error text.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"}