updating purpose-classifier data:
This commit is contained in:
+200
-200
@@ -1,200 +1,200 @@
|
||||
{"prompt": "our shared-space colocation, which drifts between headsets. is the approach sound or do we need something else?\n\n1. host creates a cloud anchor at session start and shares its id\n2. each client resolves the anchor once and stores the resulting pose\n3. all shared content is positioned relative to that stored pose\n4. each client's own tracking updates are applied on top of it\n5. there is no periodic re-resolution and no drift correction between clients\n6. relocalisation after tracking loss re-anchors to the client's own map, not the shared one\n\nusers stand around a physical table and expect virtual objects to stay on it for everyone", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.85, "slice": "pasted-context", "lang": "en"}
|
||||
{"prompt": "the same value-date logic exists in four places with three different answers:\n\n// ValueDate.java\nreturn postedAt.atZone(ZoneOffset.UTC).toLocalDate();\n\n// settlement/BatchRunner.java\nreturn LocalDate.ofInstant(postedAt, ZoneId.of(centre.timezone()));\n\n// reconciliation/Matcher.java\nreturn postedAt.atZone(ZoneId.of(\"Europe/Madrid\")).toLocalDate(); // hardcoded, one centre\n\n-- reports/daily_postings.sql\nDATE(posted_at AT TIME ZONE 'UTC')\n\nthe core banking system uses the booking centre's local date with a 23:00 cutover, which none of these implements", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "pasted-context", "lang": "en"}
|
||||
{"prompt": "mail delivery policy — concurrency, backoff, deferral limits — is inline in the SMTP worker, which is why one destination can starve every worker. extract it into something testable and configurable per destination, keeping today's behaviour as the default so we can change it deliberately rather than accidentally i'm not attached to the current approach if there's an obviously better one.", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "boundary", "lang": "en"}
|
||||
{"prompt": "statement footer still says 2025", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.1, "slice": "core", "lang": "en"}
|
||||
{"prompt": "our transactional email API, used by six internal teams, documented in a wiki page from 2023:\n\nPOST /v1/send\n body: { to, from, subject, template_id, variables, headers?, send_at?, pool? }\n pool defaults to \"transactional\"; the other pools are \"marketing\" and \"bulk\", and choosing wrong affects deliverability for everyone\n send_at more than 7 days out is silently clamped to 7 days\n a template variable that is missing renders as an empty string rather than failing\n suppression list is checked at send time, not at enqueue time, so a scheduled send may be suppressed later\n the response is 202 with a message id; delivery status arrives on a webhook or via GET /v1/messages/{id}\n rate limits are per pool per hour and are not published anywhere\n\nwrite the reference; the pool choice and the silent variable behaviour are what teams get wrong", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.65, "slice": "pasted-context", "lang": "en"}
|
||||
{"prompt": "the tinting code creates a material instance per object, which is our entire draw-call problem:\n\nvoid OnHoverEnter(GameObject go) {\n var r = go.GetComponent<Renderer>();\n r.material.color = hoverColor; // instantiates the material\n}\n\nvoid OnHoverExit(GameObject go) {\n var r = go.GetComponent<Renderer>();\n r.material.color = originalColor; // and again\n}\n\nvoid Place(GameObject prefab, Pose pose) {\n var go = Instantiate(prefab, pose.position, pose.rotation);\n go.GetComponent<Renderer>().material.SetFloat(\"_Metallic\", 0.2f); // and again\n}\n\nsame visual result required, but batching has to survive", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "pasted-context", "lang": "en"}
|
||||
{"prompt": "mail operations console is a grafana dashboard and a terminal, which is why incidents take longer than they should. build the deliverability view to the spec, including the verbatim SMTP responses per destination, and make it usable on a phone because that's where it gets opened context if it helps: this has been open since before i joined the team.", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "boundary", "lang": "en"}
|
||||
{"prompt": "a customer's statement shows a transaction twice and support can't explain it:\n\nledger entries for account 4471, 2026-07-28:\n entry 881204 DEBIT 120.00 ref=CARD-9021 posted_at=14:02:14 source=card_network\n entry 881207 DEBIT 120.00 ref=CARD-9021 posted_at=14:02:19 source=card_network\n entry 881209 CREDIT 120.00 ref=CARD-9021 posted_at=14:31:02 source=reversal\n\nthe card network sent the authorisation twice with the same reference, five seconds apart, and our idempotency check is on (ref, amount, posted_date) with posted_date derived from posted_at in local time", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.8, "slice": "pasted-context", "lang": "en"}
|
||||
{"prompt": "one value-date implementation, four callers", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "core", "lang": "en"}
|
||||
{"prompt": "what makes a posting a duplicate?", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "core", "lang": "en"}
|
||||
{"prompt": "statement rendering exists three times — PDF, HTML and CSV — each computing the running balance independently and one of them rounding negatives differently. consolidate onto one renderer with format-specific output, with the PDF as the reference because it's the regulated artefact, and diff a month of statements to prove nothing moved whatever you find, write it somewhere the next person will actually look.", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.75, "slice": "core", "lang": "en"}
|
||||
{"prompt": "batch fetch size down to 5000", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.25, "slice": "core", "lang": "en"}
|
||||
{"prompt": "instructor panel should follow on a tether", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.45, "slice": "core", "lang": "en"}
|
||||
{"prompt": "settlement thing", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "vague-eval", "lang": "en"}
|
||||
{"prompt": "ledger team loses two engineers in september and the code they own includes the settlement batch, the value-date logic and the core banking adapter. i'd like a plan for that departure specifically: what has to be written down, what should be simplified before they go, and what we accept will slow down afterwards", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.8, "slice": "boundary", "lang": "en"}
|
||||
{"prompt": "i'd like an honest read of whether our DKIM alignment is strict enough to reject mail from the old selector, and if it is, the fix — ideally without unpublishing a key that some senders still use", "purpose": "review", "secondary": "quickFix", "mixed": true, "difficulty": 0.7, "slice": "mixed", "lang": "en"}
|
||||
{"prompt": "AR content is authored by instructors in unity and shipped in the app binary, which is a release per lesson", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.8, "slice": "boundary", "lang": "en"}
|
||||
{"prompt": "one money type across the ledger", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.65, "slice": "core", "lang": "en"}
|
||||
{"prompt": "a customer's statement shows the same card transaction twice for half an hour before a reversal nets it out, and our idempotency check apparently didn't catch a repeat five seconds apart. work out exactly which part of the check let it through before we change anything, because the fix depends on whether it was the reference or the date", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.85, "slice": "core", "lang": "en"}
|
||||
{"prompt": "what does the core banking system do with a message we resend after a timeout", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "core", "lang": "en"}
|
||||
{"prompt": "hand tracking loses the pinch gesture after a few minutes and only on device:\n\n[XR] Hand tracking subsystem started, confidence high\n[XR] Frame 41882: left hand lost (confidence low), reacquired in 3 frames\n[App] PinchDetector: state=Open → Pinching (thumb-index 0.018m)\n[App] PinchDetector: state=Pinching → Open (thumb-index 0.031m)\n[App] PinchDetector: state=Open → Pinching (thumb-index 0.019m)\n[XR] Frame 88214: hand joints returning stale poses (timestamp unchanged for 12 frames)\n[App] PinchDetector: no state change for 40 seconds\n\nthe detector caches the last joint poses and compares against them, so stale poses look like a perfectly steady hand", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.8, "slice": "pasted-context", "lang": "en"}
|
||||
{"prompt": "deliverability to one provider collapsed and their postmaster tools show this:\n\nspam rate: 0.02% → 0.41% (threshold 0.30%)\ndomain reputation: high → low\nauthenticated traffic: 100%\nencrypted traffic: 100%\nIP reputation: high\ntop feedback loop complaints: \"password reset\" 88%, \"transaction alert\" 9%\n\nwe started sending password reset emails from the same domain and IP pool as marketing three weeks ago\n\nour own numbers for the same period:\n transactional volume: 1.2M/day (unchanged)\n marketing volume: 0 → 900k/day (campaign started three weeks ago)\n password reset volume: 41k/day (moved onto this pool three weeks ago)\n unsubscribe rate on marketing: 2.1%\n bounce rate overall: 0.4% → 1.9%\n\nsending IPs: 4, shared across all three streams, no subdomain separation, one DKIM selector for everything", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "pasted-context", "lang": "en"}
|
||||
{"prompt": "changelog for the AR app's 3.1 release:\n\n41c9e0b fix(hands): pinch detection now ignores stale joint poses\n88f21c0 feat(colocation): shared anchors re-resolve every 30 seconds with drift correction\nc0aa774 perf(render): objects share materials via property blocks, draw calls down from 1,482 to 210\n2e91b45 fix(anchors): relocalisation re-anchors to the shared map rather than the local one\naa30f19 feat(ui): hand menu can be summoned with either hand\n9c1d004 chore: minimum OS is now visionOS 2.2 and Android XR 1.1\n4410bb7 fix(audio): spatial audio no longer resets on app resume\nb77e910 feat(session): a session survives a headset being removed for up to 5 minutes\n\nour users are enterprise training teams; two of these change behaviour their instructors have built lessons around", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "pasted-context", "lang": "en"}
|
||||
{"prompt": "design spec for the AR training session's instructor panel, unity:\n\nInstructor panel (world-anchored, 0.6m wide, follows on a lazy tether)\n- Participant list: name, headset battery, tracking quality, current step. Rows 6cm tall, readable at 1.5m.\n- Tracking quality uses shape as well as colour — a filled, half or empty ring — because instructors are often colour-blind and always in a hurry.\n- Step control: previous / next / jump, with a confirmation for jump because it moves everyone.\n- A \"recentre everyone\" action that re-resolves the shared anchor and reports which headsets succeeded.\n- Alerts appear as a strip along the top: a participant losing tracking for more than 5 seconds, or falling behind by more than one step.\n- The panel must be summonable from either hand and dismissible with a glance away for 3 seconds.\n- Text must remain legible while the instructor is walking, which means no thin weights and no animation on the numbers.", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.8, "slice": "pasted-context", "lang": "en"}
|
||||
{"prompt": "per-destination concurrency cap of 8", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.35, "slice": "boundary", "lang": "en"}
|
||||
{"prompt": "queue age histogram on the console", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.4, "slice": "core", "lang": "en"}
|
||||
{"prompt": "delivery policy out of the SMTP code", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "core", "lang": "en"}
|
||||
{"prompt": "javadoc for the posting idempotency rule", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.4, "slice": "core", "lang": "en"}
|
||||
{"prompt": "is the pinch threshold distance-dependent?", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "boundary", "lang": "en"}
|
||||
{"prompt": "why do anchors drift between headsets?", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.8, "slice": "boundary", "lang": "en"}
|
||||
{"prompt": "accruals are a cent out mid-month", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "core", "lang": "en"}
|
||||
{"prompt": "email reputation has to recover before the statement run or a million statements land in spam, and the underlying cause is that transactional, notification and marketing mail share a domain and an IP pool. work through the separation options with the warm-up period as the awkward part, and tell me what we do about the statement run that falls in the middle of it", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.85, "slice": "core", "lang": "en"}
|
||||
{"prompt": "AnchorManager has grown to own resolution, tracking, persistence, relocalisation and debug drawing, and it's the class the drift fix has to touch. before anyone starts i'd like agreement on the split — what the pieces are, which one the fix lives in, and whether we do the split first or the fix first given the demo date", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.8, "slice": "boundary", "lang": "en"}
|
||||
{"prompt": "an auditor has asked six questions about idempotency, partial batches, adjustments, value dates, reconciliation and retention, and several of our honest answers are uncomfortable. write the controls document from the code and the runbooks, and mark clearly the ones we cannot currently substantiate rather than writing something defensible-sounding we've been burned by guessing at this before, so evidence over instinct please.", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.8, "slice": "core", "lang": "en"}
|
||||
{"prompt": "internal hand-tracking guide doesn't exist, and every developer rediscovers that TryGetJoint returns stale poses instead of failing. write the guide for internal developers covering the API's real behaviour, the confidence values nobody checks, and the frame-rate dependence of our thresholds keep it concrete — file names and line numbers are more use than principles here.", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.65, "slice": "boundary", "lang": "en"}
|
||||
{"prompt": "nobody can tell me whether our batch can commit half a transfer — the debit without the credit — given that it commits every thousand records with postings in file order rather than by transfer. read the runner and the input generation together and tell me whether that's possible, and whether it happened on the twenty-ninth", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.9, "slice": "core", "lang": "en"}
|
||||
{"prompt": "we have three ways to schedule work in the ledger service: quartz, a database poller and a cron container", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "boundary", "lang": "en"}
|
||||
{"prompt": "suppression list is checked at send time, so a scheduled statement can go to an unsubscribed address", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.4, "slice": "core", "lang": "en"}
|
||||
{"prompt": "instructor panel", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "vague-eval", "lang": "en"}
|
||||
{"prompt": "settlement batch can leave a partial day applied and our recovery is a script someone writes at four in the morning, which the operational risk register has now noticed. i'd like the options for making it restartable worked through — a checkpoint table, record-level idempotency, or regenerating a stable input file — with the month-end runtime and the eight o'clock cutover as the constraints that actually decide it", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.9, "slice": "core", "lang": "en"}
|
||||
{"prompt": "i'd like to understand what happens to an anchor when a headset relocalises after tracking loss", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.75, "slice": "core", "lang": "en"}
|
||||
{"prompt": "batch needs a checkpoint table so a failed run can resume rather than being reconstructed by hand", "purpose": "backendImpl", "secondary": null, "mixed": false, "difficulty": 0.75, "slice": "boundary", "lang": "en"}
|
||||
{"prompt": "AR app carries two input abstractions, ours and the XR toolkit's, and new code picks whichever the author saw first. move everything onto the toolkit's, and confirm whether our own layer is doing anything the toolkit doesn't before we delete it tell me if this is the wrong shape entirely, i won't be offended.", "purpose": "refactor", "secondary": "review", "mixed": true, "difficulty": 0.65, "slice": "mixed", "lang": "en"}
|
||||
{"prompt": "ledger entries table has an updated_at column that three jobs quietly set, on a table that is supposed to be immutable. stop the writes, and tell me whether any of those three jobs was relying on it for something we'd miss nobody has trusted this code for about a year, which is part of the problem.", "purpose": "quickFix", "secondary": "review", "mixed": true, "difficulty": 0.6, "slice": "mixed", "lang": "en"}
|
||||
{"prompt": "overnight settlement aborted and left the batch half-applied, which has never happened before:\n\nSEVERE [batch-worker-3] com.lumenbank.settlement.BatchRunner - batch SETTLE-20260729 failed at record 41882 of 88214\njava.sql.BatchUpdateException: ORA-00060: deadlock detected while waiting for resource\n\tat oracle.jdbc.driver.OraclePreparedStatement.executeLargeBatch(OraclePreparedStatement.java:10032)\n\tat com.lumenbank.settlement.PostingDao.applyBatch(PostingDao.java:212)\n\tat com.lumenbank.settlement.BatchRunner.run(BatchRunner.java:88)\nWARNING [batch-worker-3] rollback failed: connection closed\nSEVERE [batch-worker-3] batch marked FAILED, 41,881 postings committed, 46,333 not applied\n\nthe runner commits every 1,000 records and has no restart-from-checkpoint path", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.85, "slice": "pasted-context", "lang": "en"}
|
||||
{"prompt": "so the headset drops to 45fps whenever a user looks at the assembly area:\n\nUnity Profiler (Quest 3, 10s):\n PlayerLoop 22.1ms\n Camera.Render 14.8ms\n Drawing (opaque) 9.2ms batches: 1,482 setpass: 412\n Shadows 3.1ms\n Update.ScriptRunBehaviourUpdate 4.2ms\n AnchorManager.Update 2.9ms (GC.Alloc 812 KB)\n PostLateUpdate.UpdateAllRenderers 1.8ms\n\nWarning: 412 SetPass calls, target is under 80\nWarning: 1,482 draw calls, dynamic batching disabled by per-object material instances\n\nevery placed object gets a material instance so we can tint it on hover", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.75, "slice": "pasted-context", "lang": "en"}
|
||||
{"prompt": "outbound mail to one large provider started bouncing this morning:\n\n2026-07-29T09:02:14Z smtp-out[41221]: connecting to mx1.provider.example:25\n2026-07-29T09:02:14Z smtp-out[41221]: 220 mx1.provider.example ESMTP\n2026-07-29T09:02:15Z smtp-out[41221]: 250-STARTTLS\n2026-07-29T09:02:15Z smtp-out[41221]: TLS established, TLS1.3, X25519\n2026-07-29T09:02:15Z smtp-out[41221]: 550 5.7.1 Unauthenticated email from lumen.io is not accepted due to domain's DMARC policy\n2026-07-29T09:02:15Z smtp-out[41221]: message 8f2b1c40 bounced, queue removed\n\nour DMARC is p=reject, SPF passes, and DKIM signing was moved to a new key on monday", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.75, "slice": "pasted-context", "lang": "en"}
|
||||
{"prompt": "interest accruals are a few cents out for accounts opened mid-month, here's one:\n\naccount 4471, opened 2026-07-14, balance 250,000.00, rate 3.40% annual\nour accrual for July:\n daily_rate = 0.034 / 365 = 0.00009315068493150685\n days = 18\n accrued = 250000 * 0.00009315068493150685 * 18 = 419.1780821917808 → posted 419.18\ncore banking system's accrual for July: 419.17\ndifference: 0.01\n\nthe mainframe computes a daily amount, rounds each day to two decimals, and sums; we compute over the period and round once", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.75, "slice": "pasted-context", "lang": "en"}
|
||||
{"prompt": "ok so our SMTP queue grows without bound for one destination and the workers all end up stuck on it:\n\nqueue stats:\n total deferred: 412,882\n by destination: provider.example 411,004, everything else 1,878\n oldest deferred: 3 days\n workers busy: 32/32, all on provider.example\n\nsmtp-out log:\n 421 4.7.0 Too many concurrent connections from this IP, try again later\n (repeated, 41,882 times in the last hour)\n\nwe retry deferred messages every 60 seconds regardless of the destination's history, and we open a connection per message", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.75, "slice": "pasted-context", "lang": "en"}
|
||||
{"prompt": "la conciliación con el core bancario falla para las transferencias hechas el último día del mes:\n\ntransferencia 88412\n nuestra fecha valor: 2026-07-31T23:58:14Z\n fecha valor del core: 2026-08-01\n importe: 12.400,00 EUR\n estado en el core: liquidada\n estado en nuestro sistema: pendiente de conciliar\n\nel core opera en hora local (Madrid, UTC+2) y cierra el día contable a las 23:00; nosotros guardamos todo en UTC y conciliamos por fecha, no por instante", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.8, "slice": "pasted-context", "lang": "es"}
|
||||
{"prompt": "our on-call runbook for mail delivery is one paragraph. what the team actually does:\n\n- \"mail is slow\" almost always means one destination is deferring and workers are stuck on it\n- `mailctl queue top` shows deferred counts by destination; anything over 10,000 for one destination is the cause\n- `mailctl throttle add provider.example --concurrency 4` limits us without pausing delivery\n- pausing a destination entirely is a last resort; the queue keeps growing and we have no disk alarm on it\n- if reputation has dropped, check the postmaster tools before touching anything, because sending harder makes it worse\n- never rotate DKIM keys during an incident, which we have now done twice\n\nwrite the runbook page in the order someone paged at 3am would need it", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "pasted-context", "lang": "en"}
|
||||
{"prompt": "the AR team's list, with the customer demo in six weeks:\n\n- colocation drift correction, which is the thing the demo needs\n- pinch detection ignoring stale poses, which makes the interaction feel broken\n- draw call reduction so we hold frame rate with a realistic scene\n- AnchorManager split, without which the first item is risky to attempt\n- session resume after the headset is removed, which enterprise customers keep asking for\n- hand menu on both hands, a small thing that testers mention every session\n\ntwo engineers, six weeks, and the demo is the only immovable thing", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.85, "slice": "pasted-context", "lang": "en"}
|
||||
{"prompt": "mail runbook should be a page rather than folklore, and rotating DKIM keys during an incident should be prevented rather than discouraged. write the runbook, then add the guard to the rotation command", "purpose": "writing", "secondary": "quickFix", "mixed": true, "difficulty": 0.6, "slice": "mixed", "lang": "en"}
|
||||
{"prompt": "statement view fails an accessibility audit on seven counts including an untagged PDF. fix what we can in the app, and write the remediation plan for the PDF pipeline, which is a bigger piece of work", "purpose": "frontendImpl", "secondary": "writing", "mixed": true, "difficulty": 0.75, "slice": "mixed", "lang": "en"}
|
||||
{"prompt": "our mail sending config across environments, and staging never reproduces deliverability issues:\n\n# staging\npools: { transactional: [10.0.0.1], marketing: [10.0.0.1], bulk: [10.0.0.1] }\nper_destination_concurrency: unlimited\nretry_interval: 60s\nmax_deferrals: 100\ndkim_selector: lumen2026\nfrom_domain: staging.lumen.io\n\n# prod\npools: { transactional: [4 IPs], marketing: [4 IPs], bulk: [4 IPs] } # all the same four IPs\nper_destination_concurrency: unlimited\nretry_interval: 60s\nmax_deferrals: 100\ndkim_selector: lumen2026\nfrom_domain: lumen.io", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.4, "slice": "pasted-context", "lang": "en"}
|
||||
{"prompt": "the compliance requirement for statement delivery, which now has a date:\n\n\"Statements must be delivered to the customer's registered address of record within two business days of the statement date. Electronic delivery is permitted where the customer has consented and where delivery can be evidenced. A bounced or undeliverable statement must trigger fallback to postal delivery within one business day. Evidence of delivery, including bounce handling, must be retained for seven years and be producible per customer on request.\"\n\nwe send electronically, retain bounce records for 90 days, have no postal fallback, and cannot currently produce a per-customer delivery history. i want the plan in order of regulatory risk", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.9, "slice": "pasted-context", "lang": "en"}
|
||||
{"prompt": "mail templates are rendered by two engines depending on which team created them", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.55, "slice": "core", "lang": "en"}
|
||||
{"prompt": "a walkthrough of how a card authorisation becomes two ledger entries would help", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "boundary", "lang": "en"}
|
||||
{"prompt": "one queue abstraction, not three", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.55, "slice": "boundary", "lang": "en"}
|
||||
{"prompt": "what guarantees does the batch make about ordering of postings within one account", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "boundary", "lang": "en"}
|
||||
{"prompt": "statement view should let someone jump to a month without loading everything in between", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "boundary", "lang": "en"}
|
||||
{"prompt": "honestly the AR anchors drift apart between two headsets in the same room:\n\nheadset A: anchor \"table\" at (1.204, 0.882, -2.114) confidence 0.91\nheadset B: anchor \"table\" at (1.188, 0.884, -2.098) confidence 0.88\nshared space: session s_4471, colocation via cloud anchors\ndrift over 10 minutes: A→B distance grew from 0.4cm to 4.1cm\nrelocalisation events: A 3, B 11\n\nwe resolve the cloud anchor once at session start and never re-resolve, and each headset applies its own tracking updates on top", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.85, "slice": "pasted-context", "lang": "en"}
|
||||
{"prompt": "i'm meant to approve this before it touches the ledger, and the transaction handling worries me:\n\n@Transactional(propagation = Propagation.REQUIRES_NEW)\npublic void applyBatch(List<Posting> postings) {\n int i = 0;\n for (Posting p : postings) {\n jdbc.update(INSERT_POSTING, p.account(), p.amountCents(), p.currency(), p.ref());\n jdbc.update(UPDATE_BALANCE, p.amountCents(), p.account());\n if (++i % 1000 == 0) {\n entityManager.flush();\n entityManager.clear();\n }\n }\n}\n\nthe batch is 88,000 postings, UPDATE_BALANCE touches a row per account, and accounts appear many times in one batch in no particular order", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.85, "slice": "pasted-context", "lang": "en"}
|
||||
{"prompt": "right, the pinch detector, which is the whole interaction model of the product:\n\npublic void Update() {\n var left = handSubsystem.GetHand(Handedness.Left);\n if (!left.TryGetJoint(XRHandJointID.IndexTip, out var index)) return;\n if (!left.TryGetJoint(XRHandJointID.ThumbTip, out var thumb)) return;\n var d = Vector3.Distance(index.position, thumb.position);\n if (d < pinchThreshold && state == State.Open) { state = State.Pinching; OnPinchStart?.Invoke(); }\n else if (d > releaseThreshold && state == State.Pinching) { state = State.Open; OnPinchEnd?.Invoke(); }\n lastIndex = index; lastThumb = thumb;\n}\n\nthere's no check on joint tracking confidence or pose timestamp, and TryGetJoint returns the last known pose rather than failing when tracking is lost", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.8, "slice": "pasted-context", "lang": "en"}
|
||||
{"prompt": "quick one — our retry and backoff for outbound mail, which i think is why one destination starves the queue:\n\nfunc (w *Worker) run() {\n for msg := range w.queue {\n if err := w.deliver(msg); err != nil {\n if isTemporary(err) {\n msg.NextAttempt = time.Now().Add(60 * time.Second)\n w.queue.Requeue(msg)\n continue\n }\n w.bounce(msg, err)\n }\n }\n}\n\nthirty-two workers share one queue, requeue puts the message back at the head, and there is no per-destination concurrency limit or backoff state", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.75, "slice": "pasted-context", "lang": "en"}
|
||||
{"prompt": "bitte prüfen, bevor das in die Abstimmung mit dem Kernbanksystem geht:\n\npublic LocalDate valueDate(Instant postedAt, String bookingCentre) {\n ZoneId zone = ZoneId.of(\"UTC\");\n return postedAt.atZone(zone).toLocalDate();\n}\n\npublic boolean isDuplicate(Posting p) {\n return dao.exists(p.ref(), p.amountCents(), valueDate(p.postedAt(), p.centre()));\n}\n\ndas Kernbanksystem bucht in Ortszeit des Buchungszentrums und schließt den Buchungstag um 23:00 Uhr; unsere Duplikatsprüfung stützt sich auf ein Datum, das in UTC berechnet wird", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.8, "slice": "pasted-context", "lang": "de"}
|
||||
{"prompt": "fyi the DKIM signing configuration after monday's key rotation:\n\n# signing config\nselector: lumen2026\ndomain: lumen.io\nkey: /etc/lumen/dkim/lumen2026.private\nheaders: from:to:subject:date:message-id\ncanonicalization: relaxed/simple\n\n# DNS\nlumen2026._domainkey.lumen.io. TXT \"v=DKIM1; k=rsa; p=MIIBIjANBgkq...\" (published monday 11:04)\nlumen._domainkey.lumen.io. TXT \"v=DKIM1; k=rsa; p=MIIBIjANBgkq...\" (old selector, still published)\n\n# DMARC\n_dmarc.lumen.io. TXT \"v=DMARC1; p=reject; rua=mailto:[email protected]; adkim=s; aspf=s\"\n\nsome of our senders still use the old selector, and adkim=s means strict alignment", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.75, "slice": "pasted-context", "lang": "en"}
|
||||
{"prompt": "heads up: the design doc for our ledger's idempotency, which i suspect is where the double posting came from:\n\n## Idempotency\nA posting is uniquely identified by (reference, amount, value date). A repeated posting with the same triple is ignored.\n\n## Rationale\nThe card network guarantees a unique reference per authorisation, so this is belt and braces.\n\n## Consequences\n- A genuine repeat charge on the same day for the same amount is silently dropped.\n- Value date is computed at ingestion, in UTC.\n\n## Not covered\nReversals. Partial captures. Networks that reuse references across days.\n\nwe now know the network can send the same reference twice within seconds, and one of our booking centres is UTC+2", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.8, "slice": "pasted-context", "lang": "en"}
|
||||
{"prompt": "small thing but the query our statement generator runs per account, and month-end takes eleven hours:\n\nSELECT e.id, e.posted_at, e.amount_cents, e.currency, e.description,\n (SELECT balance_cents FROM balances b\n WHERE b.account_id = e.account_id AND b.as_of <= e.posted_at\n ORDER BY b.as_of DESC LIMIT 1) AS running_balance,\n (SELECT name FROM merchants m WHERE m.id = e.merchant_id) AS merchant\nFROM ledger_entries e\nWHERE e.account_id = $1 AND e.posted_at BETWEEN $2 AND $3\nORDER BY e.posted_at;\n\n4.1 million accounts, ledger_entries has 8.2 billion rows partitioned by month, balances is a snapshot table written daily", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.8, "slice": "pasted-context", "lang": "en"}
|
||||
{"prompt": "support's notes on the duplicate transactions, which need to become something we can send customers:\n\n- the card network occasionally sends the same authorisation twice, seconds apart\n- our duplicate check uses reference plus amount plus value date, computed in UTC\n- for our Madrid booking centre, a transaction after 22:00 local has a UTC date of the next day\n- when the two copies straddle that boundary they get different value dates and both post\n- the reversal arrives later and nets it out, so the customer's balance ends correct\n- but the statement shows three lines and the customer sees a double charge for up to 30 minutes\n- support currently explains this by hand, differently each time\n\nwrite the explanation support can send, and separately tell me which parts are bugs rather than explanations", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.65, "slice": "pasted-context", "lang": "en"}
|
||||
{"prompt": "incident notes from the settlement failure, and the regulator will want this:\n\n01:02 batch SETTLE-20260729 starts, 88,214 postings\n02:41 batch fails at record 41,882 with a database deadlock\n02:41 rollback fails, connection closed; 41,881 postings are committed\n03:10 on-call escalates to the payments lead\n04:20 decision: do not re-run the batch, apply the remainder from a filtered file\n06:55 remaining 46,333 postings applied manually with a one-off script\n08:00 reconciliation with the core banking system passes\n09:30 customer impact assessed: 1,204 accounts saw a stale balance between 02:41 and 06:55\n\nwrite the incident report for our operational risk committee, who will ask why a partial batch was possible at all", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "pasted-context", "lang": "en"}
|
||||
{"prompt": "as notas da reunião sobre a arquitetura de envio, para transformar em documento de decisão:\n\n- hoje temos um único conjunto de IPs para transacional, marketing e notificações\n- a reputação do domínio caiu depois de misturarmos recuperações de palavra-passe com marketing\n- a proposta é separar por subdomínio e por conjunto de IPs, com aquecimento progressivo\n- o aquecimento leva entre quatro e seis semanas e durante esse período a entrega é pior\n- alternativa: manter tudo junto e reduzir o volume de marketing, o que a equipa de growth recusa\n- há ainda a hipótese de usar um fornecedor externo só para marketing\n\nescreve a nota de decisão com as opções, os custos e uma recomendação", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "pasted-context", "lang": "pt"}
|
||||
{"prompt": "not urgent, but the auditor's questions on the ledger, which we've never answered in writing:\n\n1. How is a posting made idempotent, and what happens when the same reference arrives twice?\n2. Can a batch be partially applied, and how is that detected and remediated?\n3. Which staff can adjust a posted entry, and how is that evidenced?\n4. How are value dates determined across booking centres in different timezones?\n5. What is the reconciliation process against the core banking system, and what happens when it fails?\n6. How long are ledger entries retained and how is immutability assured?\n\nanswer each from the code and the runbooks, write it as a controls document, and mark anything you can't substantiate", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.8, "slice": "pasted-context", "lang": "en"}
|
||||
{"prompt": "社内向けのハンドトラッキング実装ガイドがありません。現状の挙動は次の通りです:\n\n- `TryGetJoint` はトラッキングが失われても最後の姿勢を返す。失敗しないので、呼び出し側で timestamp を確認する必要がある\n- 関節ごとに confidence 値があるが、我々のコードはどこでも見ていない\n- ピンチの閾値は 0.02m、リリースは 0.03m。ヒステリシスはあるが、手が遠いときの誤差は考慮していない\n- 片手が視界外に出ると、その手のイベントは発火しないまま状態が保持される\n- 60fps を下回るとフレーム間の移動量が大きくなり、閾値をまたぐ検出が不安定になる\n\nコード例:\n\nif (!left.TryGetJoint(XRHandJointID.IndexTip, out var index)) return;\nvar d = Vector3.Distance(index.position, thumb.position);\nif (d < pinchThreshold && state == State.Open) { ... }\n\n社内の開発者向けに、ハンドトラッキングを使う際の注意点をまとめたドキュメントを書いてください", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.65, "slice": "pasted-context", "lang": "ja"}
|
||||
{"prompt": "genuinely puzzled by this: the settlement batch's operator guide, which is three commands and a warning. reality:\n\n- the batch runs at 01:00 and takes 90 minutes on a normal night, up to four hours at month end\n- it commits every 1,000 records with no checkpoint, so a failure leaves a partial batch and no safe restart\n- the recovery procedure is a one-off script that filters the input file by what's already applied\n- that script is written from scratch each time it's needed, by whoever is on call\n- reconciliation with the core system runs at 07:00 and will fail loudly if the batch is incomplete\n- there is a hard cut-off at 08:00 after which the business day starts and manual fixes are not permitted\n\nwrite the operator guide, and be explicit that the recovery procedure is currently improvised", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.65, "slice": "pasted-context", "lang": "en"}
|
||||
{"prompt": "spotbugs and error-prone on the ledger service, gate goes on next sprint:\n\nH C SIC: Should com.lumenbank.settlement.BatchRunner$Worker be a _static_ inner class?\nM P UPM: Private method PostingDao.checkpoint(long) is never called\nH C IS2: Inconsistent synchronization of BatchRunner.progress; locked 60% of time\nM D FS: Format string should use %n rather than \\n in StatementFormatter.render()\nH B RV: Return value of Instant.plus(long, TemporalUnit) ignored in ValueDate.forCentre()\n\nerror-prone:\n [BigDecimalEquals] BigDecimal.equals compares scale; use compareTo — Accrual.java:141\n\nthe ignored return value and the BigDecimal equals both look like real money bugs", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.45, "slice": "pasted-context", "lang": "en"}
|
||||
{"prompt": "unity's analyzer and our own lint rules, before the store build:\n\nAssets/Scripts/Hands/PinchDetector.cs(22,9): warning UNT0008: Null propagation on a UnityEngine.Object\nAssets/Scripts/Anchors/AnchorManager.cs(88,13): warning UNT0001: Empty Unity message 'Start'\nAssets/Scripts/Anchors/AnchorManager.cs(141,5): warning UNT0017: SetPixels invocation is slow, consider SetPixels32\nAssets/Scripts/Render/Tinter.cs(41,7): warning LUM0002: Material instance created per object; use MaterialPropertyBlock\nAssets/Scripts/Session/Keeper.cs(66,3): warning CS4014: call not awaited\n\n5 warnings and the material one is our whole draw-call problem", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.35, "slice": "pasted-context", "lang": "en"}
|
||||
{"prompt": "for context, the DNS records for our sending domain, one of these is why some mail fails DMARC:\n\nlumen.io. TXT \"v=spf1 include:_spf.lumen.io include:sendgrid.net ~all\"\n_dmarc.lumen.io. TXT \"v=DMARC1; p=reject; adkim=s; aspf=s; rua=mailto:dmarc@lumen.io\"\nlumen2026._domainkey.lumen.io. TXT \"v=DKIM1; k=rsa; p=MIIBIjANBg...\"\nlumen._domainkey.lumen.io. TXT \"v=DKIM1; k=rsa; p=MIIBIjANBg...\"\nmail.lumen.io. A 203.0.113.41\n\nour transactional mail signs with lumen2026 and sends From: [email protected]", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.4, "slice": "pasted-context", "lang": "en"}
|
||||
{"prompt": "background: the batch job's kubernetes manifest, and it was OOMKilled twice this month:\n\nresources:\n requests: { memory: 4Gi, cpu: \"2\" }\n limits: { memory: 4Gi, cpu: \"4\" }\nenv:\n - name: JAVA_OPTS\n value: \"-Xmx3g -XX:+UseG1GC\"\n - name: BATCH_COMMIT_SIZE\n value: \"1000\"\n - name: BATCH_FETCH_SIZE\n value: \"100000\"\nactiveDeadlineSeconds: 21600\nbackoffLimit: 0\n\nfetch size of 100,000 rows into a list, then processed in commits of 1,000", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.35, "slice": "pasted-context", "lang": "en"}
|
||||
{"prompt": "dependabot on the ledger service, four open and one is a CVE:\n\nspring-boot 3.3.2 → 3.3.5 (patch; includes a fix for a transaction manager regression)\noracle jdbc 23.4 → 23.6 (minor; batch execution behaviour changed for large batches)\njackson-databind 2.17.1 → 2.18.2 (CVE-2026-10112, deserialisation of untyped collections)\nlogback 1.5.6 → 1.5.13 (minor; JNDI lookup removed entirely)\n\nour batch runner uses oracle batch execution heavily and the JDBC changelog mentions \"executeLargeBatch now fails fast on the first error rather than continuing\"", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.45, "slice": "pasted-context", "lang": "en"}
|
||||
{"prompt": "les seuils d'alerte de la file d'attente mail, on nous réveille pour rien :\n\n- alert: MailQueueDepth\n expr: mail_queue_deferred_total > 1000\n for: 5m\n labels: { severity: page }\n\n- alert: MailWorkerBusy\n expr: mail_workers_busy / mail_workers_total > 0.9\n for: 1m\n labels: { severity: page }\n\n- alert: BounceRate\n expr: rate(mail_bounced_total[1h]) / rate(mail_sent_total[1h]) > 0.05\n for: 10m\n labels: { severity: ticket }\n\nen réalité : la file dépasse 1000 chaque nuit pendant l'envoi des relevés ; les workers sont à 100% dès qu'un destinataire ralentit ; et l'incident réel (réputation effondrée, DMARC rejeté) n'a déclenché que le ticket, découvert trois jours plus tard", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.4, "slice": "pasted-context", "lang": "fr"}
|
||||
{"prompt": "this manager has accumulated everything anchor-related. same behaviour, separable pieces:\n\npublic class AnchorManager : MonoBehaviour {\n // resolves cloud anchors at session start\n // tracks local anchors and their confidence\n // owns the shared-space transform applied to all content\n // handles relocalisation after tracking loss\n // persists anchors to disk for session resume\n // drives the debug visualisation\n // subscribes to six XR subsystem events in Start and unsubscribes in none of them\n}\n\n900 lines, allocates in Update, and it's the class we most need to change for the drift fix", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "pasted-context", "lang": "en"}
|
||||
{"prompt": "nuestro código de importe monetario está escrito de tres maneras en el mismo servicio:\n\n// Posting.java\nprivate final long amountCents;\n\n// Accrual.java\nprivate final BigDecimal amount; // escala variable, comparada con equals() en dos sitios\n\n// legacy/CoreAdapter.java\nprivate final double amount; // convertido a cents al escribir, con Math.round\n\nlos tres se convierten entre sí en los límites, la comparación con equals() de BigDecimal ya causó un descuadre en junio, y el double aparece en el adaptador que habla con el core bancario", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "pasted-context", "lang": "es"}
|
||||
{"prompt": "half-year planning input, needs sequencing:\n\n- the settlement batch has no checkpoint and a partial failure is now on the operational risk register\n- our value-date handling differs from the core banking system, which is behind three separate defects\n- AR colocation drift makes multi-user training sessions unusable past ten minutes\n- email reputation has to recover before the next statement run or a million statements go to spam\n- the ledger team loses two engineers to another division in september\n- there's a regulatory audit of the ledger in january\n- the AR product has a customer demo in six weeks that has been promised multi-user", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.9, "slice": "pasted-context", "lang": "en"}
|
||||
{"prompt": "architecture ticket, thinking needed before anyone starts:\n\nLED-880 — Restartable settlement\nThe nightly batch commits every thousand records with no checkpoint, so a failure leaves a partial batch and recovery is an improvised script. The proposal is a checkpoint table and an idempotent apply, so the batch can be resumed from the last committed position. Concerns: postings are not currently idempotent at the record level, only at the (reference, amount, value date) level; the input file is not stable across reruns because it is regenerated from the source system; the batch's runtime is already close to the 08:00 cutover at month end; and the operational risk register wants a documented recovery time.", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.9, "slice": "pasted-context", "lang": "en"}
|
||||
{"prompt": "spec for the mail operations console, which we stare at during deliverability incidents:\n\nDeliverability view\n- Per-destination table: deferred count, bounce rate, average latency, current concurrency, throttle state. Sorted by deferred descending.\n- A destination row expands to show the last 20 SMTP responses verbatim, which is what actually tells you what's wrong.\n- Reputation panel per pool: spam rate, domain reputation and IP reputation, with the provider's own thresholds marked.\n- Throttle controls inline per destination, with the current value and who set it last.\n- Queue age histogram, because \"how old is the oldest message\" is the question we always end up asking.\n- Everything read-only for on-call except throttles; pausing a destination requires a second person to confirm.\n- Must work on a phone, because this is what people open from bed.", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "pasted-context", "lang": "en"}
|
||||
{"prompt": "accessibility findings on the banking app's statement view, from a regulator-mandated audit:\n\n1. The running balance column is announced as a bare number with no context, so screen reader users hear a stream of digits.\n2. Debit and credit are distinguished by colour and a minus sign rendered as an image.\n3. The date filter is a custom control with no keyboard support and no announced state.\n4. The statement PDF has no tags at all, so it is unreadable by assistive technology.\n5. Focus order jumps between the filter bar and the entry list on every filter change.\n6. Amounts use a font where 3 and 8 are hard to distinguish at the default size, and the app overrides system text size.\n7. Error messages on failed transfers are announced only visually.", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.75, "slice": "pasted-context", "lang": "en"}
|
||||
{"prompt": "design tokens versus what the banking app's transaction list actually uses:\n\ntokens:\n color.surface #FFFFFF / #0B0E11\n color.text.default #0B0E11 / #E9EEF3\n color.text.muted #5A6572\n color.amount.debit #B42318\n color.amount.credit #067647\n space 4/8/12/16/24, radius 8/12, focus 2px accent offset 2\n type: amount 17/22 tabular, body 15/20, caption 13/18\n\nthe transaction list: five hardcoded colours, amounts rendered in a proportional font so columns don't line up, a focus style removed on the row press target, and paddings of 6/11/15\n\nbring it onto the tokens, use the tabular figures for amounts, and restore the focus style", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.55, "slice": "pasted-context", "lang": "en"}
|
||||
{"prompt": "jackson CVE bump on the ledger", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.2, "slice": "core", "lang": "en"}
|
||||
{"prompt": "unpublish the old DKIM selector", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.3, "slice": "core", "lang": "en"}
|
||||
{"prompt": "hand menu on the left hand too", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.25, "slice": "core", "lang": "en"}
|
||||
{"prompt": "el importe sale sin separador de miles", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.15, "slice": "core", "lang": "es"}
|
||||
{"prompt": "marketing off the transactional IPs", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.4, "slice": "boundary", "lang": "en"}
|
||||
{"prompt": "BigDecimal equals in Accrual.java", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.35, "slice": "boundary", "lang": "en"}
|
||||
{"prompt": "BounceRate should page, not ticket", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.3, "slice": "boundary", "lang": "en"}
|
||||
{"prompt": "Xmx passt nicht zum Memory-Limit", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.3, "slice": "boundary", "lang": "de"}
|
||||
{"prompt": "ignored return value in ValueDate", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.35, "slice": "boundary", "lang": "en"}
|
||||
{"prompt": "tracking quality needs a shape, not a colour", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.3, "slice": "core", "lang": "en"}
|
||||
{"prompt": "amounts need tabular figures", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.25, "slice": "core", "lang": "en"}
|
||||
{"prompt": "expand a destination to see SMTP replies", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.4, "slice": "core", "lang": "en"}
|
||||
{"prompt": "our mail workers, queue and throttling are one package with the policy inline:\n\nfunc (w *Worker) deliver(msg *Message) error {\n conn, err := smtp.Dial(msg.Destination.MX[0] + \":25\") // no pooling, no per-destination limit\n ...\n if isTemporary(err) {\n msg.NextAttempt = time.Now().Add(60 * time.Second) // policy inline\n return w.queue.Requeue(msg)\n }\n ...\n}\n\ni want the delivery policy — concurrency per destination, backoff schedule, deferral limits — expressed somewhere it can be tested and changed without touching the SMTP code, with today's behaviour as the default", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.65, "slice": "pasted-context", "lang": "en"}
|
||||
{"prompt": "the core banking system's interface spec, which we implement against:\n\nMQ-based, fixed-width records, one message per posting\n fields: account (10), amount (13, implied 2 decimals, sign in the last byte), currency (3), value date (8, YYYYMMDD, booking centre local), reference (16), centre (4)\n the core acknowledges each message with a status record; an unacknowledged message must be resent with the same reference\n a resent message that the core already applied returns status 'DUP' and must be treated as success\n the daily cutover is 23:00 booking centre local; messages after cutover carry the next business date\n business dates skip weekends and the centre's holiday calendar, which we receive as a yearly file\n the core rejects a batch if any record's value date is more than one business day in the past", "purpose": "backendImpl", "secondary": null, "mixed": false, "difficulty": 0.85, "slice": "pasted-context", "lang": "en"}
|
||||
{"prompt": "mail console should show the oldest deferred message per destination, which is what we always ask", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.45, "slice": "boundary", "lang": "en"}
|
||||
{"prompt": "手のメニューが片手でしか出せません", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.3, "slice": "core", "lang": "ja"}
|
||||
{"prompt": "minus signs are rendered as images", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.25, "slice": "boundary", "lang": "en"}
|
||||
{"prompt": "date filter has no keyboard support", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.35, "slice": "boundary", "lang": "en"}
|
||||
{"prompt": "app overrides system text size", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.3, "slice": "boundary", "lang": "en"}
|
||||
{"prompt": "console is unusable on a phone", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.4, "slice": "boundary", "lang": "en"}
|
||||
{"prompt": "property blocks instead of material instances", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "core", "lang": "en"}
|
||||
{"prompt": "un seul rendu de relevé, trois formats", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "core", "lang": "fr"}
|
||||
{"prompt": "`posted_at` naming, be consistent", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.3, "slice": "boundary", "lang": "en"}
|
||||
{"prompt": "split relocalisation out of AnchorManager", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "boundary", "lang": "en"}
|
||||
{"prompt": "inline `isTemporary`, one caller", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.2, "slice": "boundary", "lang": "en"}
|
||||
{"prompt": "changelog for the AR 3.1 release", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.3, "slice": "core", "lang": "en"}
|
||||
{"prompt": "nota interna sobre a separação de IPs", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.4, "slice": "core", "lang": "pt"}
|
||||
{"prompt": "document the 23:00 cutover rule", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.45, "slice": "boundary", "lang": "en"}
|
||||
{"prompt": "summarise the checkpoint proposal", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "boundary", "lang": "en"}
|
||||
{"prompt": "PR body for the drift correction", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.3, "slice": "boundary", "lang": "en"}
|
||||
{"prompt": "can a batch commit half a transfer?", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.8, "slice": "core", "lang": "en"}
|
||||
{"prompt": "¿por qué el DMARC rechaza algunos correos?", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.65, "slice": "core", "lang": "es"}
|
||||
{"prompt": "walk me through the reconciliation job", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "boundary", "lang": "en"}
|
||||
{"prompt": "pinch stops working after a few minutes", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.75, "slice": "core", "lang": "en"}
|
||||
{"prompt": "one destination starves the mail queue", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "boundary", "lang": "en"}
|
||||
{"prompt": "warum bucht der Batch nur die Hälfte?", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.8, "slice": "boundary", "lang": "de"}
|
||||
{"prompt": "endpoint for a customer's delivery history", "purpose": "backendImpl", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "core", "lang": "en"}
|
||||
{"prompt": "keep going on it", "purpose": "backendImpl", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "vague-eval", "lang": "en"}
|
||||
{"prompt": "fewer alerts", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.45, "slice": "vague-eval", "lang": "en"}
|
||||
{"prompt": "whatever the auditors will ask about", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "vague-eval", "lang": "en"}
|
||||
{"prompt": "lo del correo, sigue", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.55, "slice": "vague-eval", "lang": "es"}
|
||||
{"prompt": "anchors, again", "purpose": "debugging", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "vague-eval", "lang": "en"}
|
||||
{"prompt": "tidy the ledger code", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "vague-eval", "lang": "en"}
|
||||
{"prompt": "same as before", "purpose": "backendImpl", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "vague-eval", "lang": "en"}
|
||||
{"prompt": "controls doc", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "vague-eval", "lang": "en"}
|
||||
{"prompt": "something safe for a friday", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.4, "slice": "vague-eval", "lang": "en"}
|
||||
{"prompt": "another set of eyes", "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": "onto the next one", "purpose": "backendImpl", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "vague-eval", "lang": "en"}
|
||||
{"prompt": "value dates disagree with the core banking system in three different ways depending on which of our four implementations you hit, and each disagreement has produced a defect. rather than fix them one at a time i want a position on where value date should be computed, who owns the business calendar, and how we'd prove agreement with the core continuously rather than at month end", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.9, "slice": "core", "lang": "en"}
|
||||
{"prompt": "multi-user AR sessions are unusable past about ten minutes because shared anchors drift, and the demo in six weeks has been promised multi-user. i want the approach decided properly — periodic re-resolution, relative correction between clients, or a different colocation mechanism entirely — with an honest view of what's achievable in six weeks versus what's the real fix", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.85, "slice": "core", "lang": "en"}
|
||||
{"prompt": "transactional email API is used by six teams from a wiki page written before the pools existed, and choosing the wrong pool degrades deliverability for everyone. write the reference documentation properly, with the pool guidance up front, the silent behaviours stated, and the rate limits published rather than discovered the last person who touched this left, so there's nobody to ask.", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.65, "slice": "core", "lang": "en"}
|
||||
{"prompt": "settlement batch's operator guide is three commands and a warning, while the real recovery procedure is improvised from scratch each time by whoever is on call at four in the morning. write the guide honestly, including that the recovery script does not exist, because pretending otherwise is how we got here i'd like enough detail that i can hand it to someone else to finish.", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.65, "slice": "core", "lang": "en"}
|
||||
{"prompt": "support explains our duplicate-transaction behaviour differently every time because nobody has written down what actually happens with the reference, the value date and the reversal. write the explanation they can send to a customer, in plain language, without implying the customer was charged twice when the balance was never wrong if the answer is that it's fine as it is, that's a useful answer too.", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.65, "slice": "boundary", "lang": "en"}
|
||||
{"prompt": "idempotency design doc says a card reference is unique per authorisation and treats that as belt and braces, which we now know is wrong in at least two ways. read it against the code and the incident and tell me which of its other assumptions are load-bearing, because i suspect the value-date one is worse than the reference one", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.85, "slice": "boundary", "lang": "en"}
|
||||
{"prompt": "colocation approach resolves a cloud anchor once and never revisits it, which the drift numbers suggest is the whole problem, but i'd like that confirmed rather than assumed before we commit six weeks to a fix. read the anchor lifecycle and the relocalisation path and tell me where the error actually accumulates a rough ordering matters more to me than a complete answer right now.", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.85, "slice": "boundary", "lang": "en"}
|
||||
{"prompt": "money is represented as long cents, BigDecimal and double in the same service, converted at every boundary, and one BigDecimal equals comparison already caused a reconciliation break. settle on one representation, convert at the edges only, and prove that every posting from last month produces an identical amount afterwards this is the third time it's bitten us and i'd like it to be the last.", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.8, "slice": "core", "lang": "en"}
|
||||
{"prompt": "instructor panel is what makes multi-user sessions manageable and right now it's a debug canvas with a participant count. build it to the spec — tracking quality as shape and colour, step control with confirmation, recentre-everyone with per-headset results — and make sure it's legible while the instructor walks", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.8, "slice": "core", "lang": "en"}
|
||||
{"prompt": "before we make the batch restartable i want the checkpoint semantics agreed — what a checkpoint covers, what happens to a partially applied commit, how the input file is made stable — and then the checkpoint table and resume path implemented against it", "purpose": "planning", "secondary": "backendImpl", "mixed": true, "difficulty": 0.9, "slice": "mixed", "lang": "en"}
|
||||
{"prompt": "IP and domain separation for mail needs a plan with a warm-up schedule, and it needs the transactional subdomain standing up now so the warm-up can start. give me the plan, then do the subdomain, DKIM and SPF setup for it i'd rather have the reasoning written down than a quick answer.", "purpose": "planning", "secondary": "backendImpl", "mixed": true, "difficulty": 0.8, "slice": "mixed", "lang": "en"}
|
||||
{"prompt": "anchor drift needs a proper design and the demo needs something in six weeks. work out the correction approach with me, then implement periodic re-resolution as the shippable subset, keeping the full design written down for afterwards", "purpose": "planning", "secondary": "frontendImpl", "mixed": true, "difficulty": 0.85, "slice": "mixed", "lang": "en"}
|
||||
{"prompt": "unsere Wertstellungslogik existiert viermal und weicht dreimal vom Kernbanksystem ab. Ich hätte gern zuerst eine Festlegung, wo das Datum berechnet wird und wem der Buchungskalender gehört, und danach die Zusammenführung an einer Stelle", "purpose": "planning", "secondary": "refactor", "mixed": true, "difficulty": 0.85, "slice": "mixed", "lang": "de"}
|
||||
{"prompt": "our statement rendering is duplicated for PDF, HTML email and the CSV export:\n\n// StatementPdf.java — iterates entries, formats amounts with a NumberFormat in the user's locale\n// StatementHtml.java — iterates entries, formats amounts with String.format(\"%,.2f\")\n// StatementCsv.java — iterates entries, writes raw cents\n\nall three compute the running balance independently; the PDF one is the regulated artefact; and the HTML one has a rounding difference on negative amounts that a customer noticed last month", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.65, "slice": "pasted-context", "lang": "en"}
|
||||
{"prompt": "the schema we agreed for delivery evidence, now it needs building:\n\nCREATE TABLE delivery_events (\n id bigserial PRIMARY KEY,\n message_id uuid NOT NULL,\n customer_id uuid NOT NULL,\n kind text NOT NULL CHECK (kind IN ('queued','sent','delivered','deferred','bounced','complained','suppressed')),\n destination text NOT NULL,\n smtp_response text,\n occurred_at timestamptz NOT NULL,\n provider_id text\n);\nCREATE INDEX ON delivery_events (customer_id, occurred_at DESC);\n\nseven year retention, immutable once written, must be producible per customer within a working day, and must drive an automatic postal fallback when a statement bounces — which means the bounce has to be classified as permanent or temporary reliably", "purpose": "backendImpl", "secondary": null, "mixed": false, "difficulty": 0.8, "slice": "pasted-context", "lang": "en"}
|
||||
{"prompt": "delivery evidence has a seven-year retention requirement and no design. decide with me what we record, how it stays immutable and how the postal fallback is triggered, then build the event write path", "purpose": "planning", "secondary": "backendImpl", "mixed": true, "difficulty": 0.85, "slice": "mixed", "lang": "en"}
|
||||
{"prompt": "email API reference has to exist before another team picks the wrong pool, and while writing it please confirm whether send_at really clamps silently at seven days, because two teams believe it errors", "purpose": "writing", "secondary": "review", "mixed": true, "difficulty": 0.6, "slice": "mixed", "lang": "en"}
|
||||
{"prompt": "hand-tracking guide needs writing and i suspect it will surface behaviours we should fix rather than document — the stale pose one especially. write the guide, and give me that list separately", "purpose": "writing", "secondary": "review", "mixed": true, "difficulty": 0.65, "slice": "mixed", "lang": "en"}
|
||||
{"prompt": "escribe la guía del operador para el batch de liquidación y comprueba en el código si el commit cada mil registros puede partir una transferencia en dos, porque de eso depende todo lo demás", "purpose": "writing", "secondary": "review", "mixed": true, "difficulty": 0.75, "slice": "mixed", "lang": "es"}
|
||||
{"prompt": "tinting via material instances is the whole draw-call problem and the fix is property blocks. make the change, and document the rendering conventions so the next feature doesn't reintroduce it", "purpose": "refactor", "secondary": "writing", "mixed": true, "difficulty": 0.6, "slice": "mixed", "lang": "en"}
|
||||
{"prompt": "three queue abstractions should become one, and i'd like to know first whether any of them is actually load-bearing for ordering guarantees. check that, then consolidate", "purpose": "refactor", "secondary": "review", "mixed": true, "difficulty": 0.7, "slice": "mixed", "lang": "en"}
|
||||
{"prompt": "AnchorManager needs splitting before the drift work lands. do the split, then write the short note on which class owns the shared transform, because that's the question every bug report ends up being about", "purpose": "refactor", "secondary": "writing", "mixed": true, "difficulty": 0.7, "slice": "mixed", "lang": "en"}
|
||||
{"prompt": "accruals differ from the core system by a cent for accounts opened mid-month, which looks like a rounding-frequency difference. confirm that from the code, then align our calculation and tell me how many accounts are affected historically", "purpose": "debugging", "secondary": "backendImpl", "mixed": true, "difficulty": 0.8, "slice": "mixed", "lang": "en"}
|
||||
{"prompt": "queue starves whenever one destination defers, and thirty-two workers all end up on it. diagnose it properly, then implement per-destination concurrency so a slow provider can't take the whole sender down", "purpose": "debugging", "secondary": "backendImpl", "mixed": true, "difficulty": 0.75, "slice": "mixed", "lang": "en"}
|
||||
{"prompt": "headset drops to 45fps in one area and the profiler blames draw calls, but i want the cause confirmed rather than inferred. work through it, then do whichever fix the evidence supports", "purpose": "debugging", "secondary": "refactor", "mixed": true, "difficulty": 0.7, "slice": "mixed", "lang": "en"}
|
||||
{"prompt": "transaction list ignores the tokens and renders amounts in a proportional font. bring it onto the tokens with tabular figures, and tell me whether the amount column width changes enough to affect the layout on small phones", "purpose": "frontendImpl", "secondary": "review", "mixed": true, "difficulty": 0.55, "slice": "mixed", "lang": "en"}
|
||||
{"prompt": "core banking adapter needs to handle the DUP status as success rather than an error, and we should agree what a resend means for our own idempotency first. decide that, then implement", "purpose": "backendImpl", "secondary": "planning", "mixed": true, "difficulty": 0.7, "slice": "mixed", "lang": "en"}
|
||||
{"prompt": "rename `Posting.ref`, it's the card network's reference in one place and ours in another", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "boundary", "lang": "en"}
|
||||
{"prompt": "could you explain how a reversal is matched to the original posting when the reference repeats", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "core", "lang": "en"}
|
||||
{"prompt": "is our suppression list checked at enqueue as well as at send, or only at send", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.55, "slice": "core", "lang": "en"}
|
||||
{"prompt": "why does the statement generator take eleven hours at month end when it's one query per account", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "boundary", "lang": "en"}
|
||||
{"prompt": "missing template variables should fail loudly rather than rendering as an empty string, which is how one team shipped a statement email with a blank amount. change the default, give the forty-odd templates that rely on the current behaviour an explicit opt-out, and tell me which ones actually need it keep it concrete — file names and line numbers are more use than principles here.", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "boundary", "lang": "en"}
|
||||
{"prompt": "pouvez-vous m'expliquer comment la date de valeur est calculée pour un centre en UTC+2 ?", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.65, "slice": "boundary", "lang": "fr"}
|
||||
{"prompt": "docs/settlement.md describes a restartable batch, which is aspirational rather than true", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.45, "slice": "core", "lang": "en"}
|
||||
{"prompt": "a short note on why we're separating the sending domains, for the decision log", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.4, "slice": "core", "lang": "en"}
|
||||
{"prompt": "API changelog needs an entry for the pool parameter becoming required", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.4, "slice": "boundary", "lang": "en"}
|
||||
{"prompt": "javadoc on applyBatch promises atomicity that the commit-every-thousand loop doesn't provide", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "boundary", "lang": "en"}
|
||||
{"prompt": "write the customer note about statements moving to a new sending domain", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.4, "slice": "boundary", "lang": "en"}
|
||||
{"prompt": "health check reports the batch service healthy while the last run failed halfway", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.35, "slice": "core", "lang": "en"}
|
||||
{"prompt": "staging sends from a single IP for all three pools, which is why pool bugs never appear there", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.3, "slice": "boundary", "lang": "en"}
|
||||
{"prompt": "how should we handle a booking centre in a timezone we don't currently support", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.75, "slice": "core", "lang": "en"}
|
||||
{"prompt": "what's the right way to test money code where the failure mode is a regulatory finding", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.8, "slice": "core", "lang": "en"}
|
||||
{"prompt": "i want a position on whether AR session state should live on the headset or the server", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.75, "slice": "core", "lang": "en"}
|
||||
{"prompt": "two teams want to send mail through us with their own domains, what should the tenancy model be", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.75, "slice": "boundary", "lang": "en"}
|
||||
{"prompt": "we need a plan for supporting a second core banking system for the acquired bank", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.85, "slice": "boundary", "lang": "en"}
|
||||
{"prompt": "what should happen to a scheduled send when the template is edited before it goes out", "purpose": "planning", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "boundary", "lang": "en"}
|
||||
{"prompt": "an endpoint that returns a posting's full lineage — source message, batch, reversals, adjustments", "purpose": "backendImpl", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "core", "lang": "en"}
|
||||
{"prompt": "shared anchors should re-resolve on a timer with a drift correction applied between clients", "purpose": "backendImpl", "secondary": null, "mixed": false, "difficulty": 0.8, "slice": "core", "lang": "en"}
|
||||
{"prompt": "deliverability view needs a per-pool reputation panel with the provider's thresholds marked", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "core", "lang": "en"}
|
||||
{"prompt": "participant list should show who has fallen behind a step, not just who is connected", "purpose": "frontendImpl", "secondary": null, "mixed": false, "difficulty": 0.5, "slice": "boundary", "lang": "en"}
|
||||
{"prompt": "whatever's safe before month end", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.45, "slice": "vague-eval", "lang": "en"}
|
||||
{"prompt": "next bit of the mail work", "purpose": "backendImpl", "secondary": null, "mixed": false, "difficulty": 0.55, "slice": "vague-eval", "lang": "en"}
|
||||
{"prompt": "batch runner and the online posting path each update balances with different locking, which is why a batch running during business hours can deadlock against normal traffic. bring them onto one path with one locking strategy, and tell me which of the two behaviours we're actually keeping, because they differ on ordering within an account", "purpose": "refactor", "secondary": "review", "mixed": true, "difficulty": 0.8, "slice": "mixed", "lang": "en"}
|
||||
{"prompt": "i'd like an honest read on whether a support user can adjust a posted entry without leaving an audit trail, given the admin tooling and the direct database access two people still have, and the smallest change that closes it before january assume whoever picks it up next has no context beyond what you write.", "purpose": "review", "secondary": "planning", "mixed": true, "difficulty": 0.8, "slice": "mixed", "lang": "en"}
|
||||
{"prompt": "per-destination backoff state has to survive a restart, and the shape of that state depends on whether we treat a destination as an MX host or a domain. decide that with me — the two behave differently for providers with shared infrastructure — then implement it the sooner we know roughly how big this is, the better for planning.", "purpose": "backendImpl", "secondary": "planning", "mixed": true, "difficulty": 0.7, "slice": "mixed", "lang": "en"}
|
||||
{"prompt": "internal page on the reconciliation process stops at \"the job compares both sides\" and everything that matters — what a break is, who investigates, what the cutover time means — is folklore. write the page properly, following one break from detection to resolution, and name the systems and people involved at each step i've already spent an afternoon on it and got nowhere useful.", "purpose": "writing", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "boundary", "lang": "en"}
|
||||
{"prompt": "AR session times out sixty seconds after a headset is removed, while enterprise customers run training where instructors take headsets off routinely for five minutes at a time. raise the timeout, make it configurable per deployment, and make sure a session that does expire tells participants why rather than simply disappearing this has come up in three separate reviews now and never gets done.", "purpose": "quickFix", "secondary": null, "mixed": false, "difficulty": 0.45, "slice": "boundary", "lang": "en"}
|
||||
{"prompt": "mail templates are rendered by two engines depending on which team created them, which means a variable that works in one silently produces nothing in the other, and neither team knows which engine their template uses. consolidate onto the newer engine, migrate the older templates, and diff the rendered output for a sample of each so nothing changes under a customer's nose", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.65, "slice": "core", "lang": "en"}
|
||||
{"prompt": "ledger service schedules work three ways — quartz, a database poller and a cron container — and which one a job uses depends entirely on when it was written. settle on one mechanism, migrate the jobs, and make sure the ones with strict timing relative to the settlement batch keep their ordering guarantees it doesn't have to be elegant, it has to be defensible in a review.", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "core", "lang": "en"}
|
||||
{"prompt": "`Posting.ref` means the card network's reference in the ingestion path and our own generated reference everywhere else, which is exactly the confusion behind the duplicate posting incident. give the two concepts different names throughout, keep the database columns as they are for now, and flag any place where the ambiguity is currently load-bearing", "purpose": "refactor", "secondary": null, "mixed": false, "difficulty": 0.6, "slice": "core", "lang": "en"}
|
||||
{"prompt": "nobody can tell me what the reconciliation job does when it finds a break at month end, specifically whether it stops, continues, or quietly writes an adjustment. read the job and its runbook together and tell me what really happens, and how many breaks went through that path last quarter flag anything you'd want to change before doing it rather than after.", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.7, "slice": "boundary", "lang": "en"}
|
||||
{"prompt": "statement generator issues one query per account with two correlated subqueries inside it, and month end takes eleven hours against a nine hour window. before anyone rewrites it i want to know where the time actually goes and whether the balances snapshot table is being used at all there's no rush on this week specifically, but it keeps costing us time.", "purpose": "review", "secondary": null, "mixed": false, "difficulty": 0.75, "slice": "core", "lang": "en"}
|
||||
{"prompt": "suppression list is checked at send time rather than at enqueue, so a statement scheduled a week ahead can go to an address that unsubscribed yesterday, which is a compliance problem rather than an inconvenience. check at both points, keep the send-time check as the authority, and record which check suppressed a message the last person who touched this left, so there's nobody to ask.", "purpose": "backendImpl", "secondary": null, "mixed": false, "difficulty": 0.55, "slice": "core", "lang": "en"}
|
||||
{"prompt":"One contained cleanup in projects/longbow/cmd/exporter/main.py: remove the obsolete LongbowPineMetricsFlow import and let the existing formatter settle the blank line.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"}
|
||||
{"prompt":"LongbowMoonlitSDKCoordinator: diagnose, then correct","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"}
|
||||
{"prompt":"Apparently: Check LongbowEmberRelayService's trust boundary","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"}
|
||||
{"prompt":"Before we approve LongbowMarbleTokenStore, assess whether an accessibility label that reads the internal enum is an actual correctness risk or merely confusing structure. I want your judgment and walkthrough, not new documentation.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"}
|
||||
{"prompt":"This should remain a deliberately small patch: LongbowHarborIndexStore has one known configuration mistake in projects/longbow/internal/auth/refresh.go, 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- leave generated files and vendored code alone\n- stay compatible with the existing Playwright deployment\n- keep the work scoped to LongbowHarborIndexStore and its direct tests\n\nThe relevant code crosses billing, Elixir, Android. Prefer evidence from the repository and make any assumption explicit.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"}
|
||||
{"prompt":"Before touching projects/longbow/infra/modules/edge/main.tf, propose how to retire its legacy format while old clients remain active for ninety days and operators retain a reversible escape hatch.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"}
|
||||
{"prompt":"Lately: projects/longbow/web/components/FilterDrawer.vue 里的 LongbowAmberFilterStore 最近在 Playwright 流程中出现间歇性问题。 请完成 responsive layout、空状态、retry、键盘焦点、dark mode 和 reduced motion。\n\n约束：\n- 继续使用 Playwright\n- 保持兼容性和取消语义\n- 改动只限于 LongbowAmberFilterStore","purpose":"frontendImpl","secondary":"debugging","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"zh"}
|
||||
{"prompt":"Read projects/longbow/crates/index/src/segment.rs and tell me whether LongbowJuniperCLIFlow can acknowledge work before its durable write completes; this is a read-only safety pass. I want your judgment and walkthrough, not new documentation.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"}
|
||||
{"prompt":"Ticket OPS-52139: retire the legacy replay path for LongbowSummitProxyFlow\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 LongbowSummitProxyFlow 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":"LongbowMarbleTokenCoordinator: handle the lingering thing","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"}
|
||||
{"prompt":"Oddly: // projects/longbow/Sources/CLI/Commands/Doctor.swift\nfinal class LongbowBasilRunnerFlowCoordinator {\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 LongbowBasilRunnerFlow 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":"LongbowMapleQueueCoordinator: something is off here","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"}
|
||||
{"prompt":"On compact widths, LongbowMarbleTokenService's filter drawer should slide over the results, trap focus, and expose a visible close control without changing the desktop layout.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"}
|
||||
{"prompt":"Responsive layout for LongbowCinderAuthStore","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"}
|
||||
{"prompt":"Fresh release brief for LongbowCraneWorkspaceCoordinator:\n- primary outcome: change LongbowCraneWorkspaceCoordinator's known staging timeout from 15 to 30 seconds\n- companion outcome: capture the contract and rollback note for consumers\n- repository entry point: projects/longbow/lib/codec/frame.cc\n- platform constraint: Core Data\n- known complication: a deadlock that appears only during shutdown\n\nBoth results are required, but they should remain independently reviewable. Leave generated files and vendored code alone; 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":"quickFix","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"}
|
||||
{"prompt":"Fresh release brief for LongbowNovaPickerCoordinator:\n- primary outcome: assess ownership and failure handling in projects/longbow/cmd/exporter/main.py\n- companion outcome: capture the contract and rollback note for consumers\n- repository entry point: projects/longbow/cmd/exporter/main.py\n- platform constraint: Redis Streams\n- known complication: a flaky snapshot caused by locale-dependent sorting\n\nBoth results are required, but they should remain independently reviewable. Leave generated files and vendored code alone; 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":"review","secondary":"writing","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"}
|
||||
{"prompt":"LongbowAtlasSearchService'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.2,"slice":"core","lang":"en"}
|
||||
{"prompt":"The minimum supported React 19 version in projects/longbow/db/migrations/20260730_events.sql is one patch behind the lockfile. Align that single value and regenerate only the affected metadata.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"}
|
||||
{"prompt":"Please turn LongbowWrenExportStore's existing tests into a short contract reference, covering pagination, malformed input, authorization, and retry semantics without copying test code.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"}
|
||||
{"prompt":"projects/longbow/db/migrations/20260730_events.sql now contains LongbowCedarPolicyStore'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":"En projects/longbow/apps/console/routes/usage.svelte, LongbowCloudReconcilerStore tiene un problema intermitente en el flujo de React 19. Sigue queue, scheduler y cancelación, compara hipótesis y encuentra la causa antes de proponer cambios.\n\nRestricciones:\n- seguir con React 19\n- conservar compatibilidad y cancelación\n- limitar el cambio a LongbowCloudReconcilerStore","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"es"}
|
||||
{"prompt":"Currently: # projects/longbow/infra/modules/edge/main.tf\n[worker.longbowbirchmigratorflow]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.longbowbirchmigratorflow.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.longbowbirchmigratorflow.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.LongbowBirchMigratorFlow.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-52128\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\nAlign LongbowBirchMigratorFlow'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":"Match LongbowMoonlitSDKStore's dark theme","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"}
|
||||
{"prompt":"Test Suite 'LongbowLedgerGateCoordinatorTests' started at 2026-07-30 09:22:14.018\nTest Case '-[LongbowLedgerGateCoordinatorTests testRestoresSelectionAfterBackgrounding]' started.\nprojects/longbow/web/components/FilterDrawer.vue:144: error: -[LongbowLedgerGateCoordinatorTests 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 '-[LongbowLedgerGateCoordinatorTests 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\n上のコンテキストを基に依頼された作業を行い、API、互換性、rollback を維持し、根拠と判断を明確にしてください。 Find the source of this LongbowLedgerGateCoordinator 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":"LongbowWrenExportCoordinator: the docs need something","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.2,"slice":"vague-eval","lang":"en"}
|
||||
{"prompt":"Summarize the LongbowRavenSessionService changes","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"}
|
||||
{"prompt":"Today: This should remain a deliberately small patch: LongbowRainfallDBService has one known configuration mistake in projects/longbow/workers/thumbnail/consumer.ex, 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- leave generated files and vendored code alone\n- stay compatible with the existing Core Data deployment\n- keep the work scoped to LongbowRainfallDBService and its direct tests\n\nThe relevant code crosses billing, Elixir, Android. Prefer evidence from the repository and make any assumption explicit.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"}
|
||||
{"prompt":"Architect a gradual ownership transfer for LongbowBeaconStoreStore across two teams, including module seams, temporary interfaces, observability, handoff criteria, and rollback responsibility.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"}
|
||||
{"prompt":"Architect a gradual ownership transfer for LongbowWrenExportService across two teams, including module seams, temporary interfaces, observability, handoff criteria, and rollback responsibility.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"}
|
||||
{"prompt":"EXPLAIN (ANALYZE, BUFFERS)\nSELECT e.tenant_id, e.stream_id, max(e.sequence)\nFROM event_log e\nJOIN active_streams s\n ON s.tenant_id = e.tenant_id AND s.id = e.stream_id\nWHERE e.tenant_id = 't_52133'\n AND e.created_at >= now() - interval '24 hours'\nGROUP BY e.tenant_id, e.stream_id;\n\nHashAggregate (cost=184922.10..185011.81 rows=8971 width=40) (actual time=8421.294..8422.551 rows=123 loops=1)\n Group Key: e.tenant_id, e.stream_id\n Batches: 1 Memory Usage: 945kB\n -> Hash Join (cost=2118.42..181004.17 rows=522391 width=32) (actual time=42.118..8279.405 rows=918412 loops=1)\n Hash Cond: ((e.tenant_id = s.tenant_id) AND (e.stream_id = s.id))\n -> Bitmap Heap Scan on event_log e (actual time=18.602..7922.884 rows=1261044 loops=1)\n Recheck Cond: (tenant_id = 't_52133'::text)\n Filter: (created_at >= (now() - '24:00:00'::interval))\n Rows Removed by Filter: 8045512\nPlanning Time: 2.814 ms\nExecution Time: 8423.104 ms\n\nPostgreSQL 17.2, default_statistics_target=100. The same query was under 300 ms last week, no migration landed, and an ANALYZE temporarily returns it to normal.\n\nDetermine why LongbowEchoRegistryFlow produces this result. Trace ordering, cancellation, shared state, and scheduler behavior; identify the root cause before suggesting a patch.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"}
|
||||
{"prompt":"Split LongbowOpalRouterService without behavior changes","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"}
|
||||
{"prompt":"Give LongbowCinderAuthService a README example","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"}
|
||||
{"prompt":"Context: // projects/longbow/Sources/CLI/Commands/Doctor.swift\nfinal class LongbowFrostPanelCoordinatorCoordinator {\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 LongbowFrostPanelCoordinator; flag semantic changes and missing coverage with exact evidence, keeping this a read-only pass.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"pasted-context","lang":"en"}
|
||||
{"prompt":"Security flagged LongbowPineMetricsService for a read-only pass because its Redis Streams 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- leave generated files and vendored code alone\n- retain the current Redis Streams operational envelope\n\nThis repository spans billing, Elixir, Android; use its existing conventions rather than importing a new abstraction.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"}
|
||||
{"prompt":"Describe LongbowBirchMigratorService's error envelope","purpose":"review","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"}
|
||||
{"prompt":"Give LongbowLedgerGateStore'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":"Two deliverables are holding up LongbowOpalRouterCoordinator. First, finish LongbowOpalRouterCoordinator's responsive empty and retry states. In the same workstream, correct the known stale timeout beside it. The relevant starting point is projects/longbow/crates/index/src/segment.rs, which follows Terraform conventions and currently suffers from an empty state that flashes before cached data arrives. Leave generated files and vendored code alone.\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":"frontendImpl","secondary":"quickFix","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"}
|
||||
{"prompt":"Trace LongbowBirchMigratorStore's memory growth","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"}
|
||||
{"prompt":"Is there a cleaner way to separate LongbowBeaconStoreService'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":"Decouple LongbowPrismCacheService's storage policy","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"}
|
||||
{"prompt":"PM needs a concise migration note for LongbowFrostPanelStore, 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":"LongbowFernSnapshotFlow 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":"Our support and SDK teams keep answering the same questions about LongbowAsterWebhookService, but the current prose in projects/longbow/Sources/CLI/Commands/Doctor.swift 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- leave generated files and vendored code alone\n- stay compatible with the existing Redis Streams deployment\n- keep the work scoped to LongbowAsterWebhookService and its direct tests\n\nThe relevant code crosses billing, Elixir, Android. Prefer evidence from the repository and make any assumption explicit.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"}
|
||||
{"prompt":"The behavior of LongbowCopperBridgeStore is stable, yet consumers are reconstructing its contract from tests, Slack threads, and scattered comments in projects/longbow/packages/api/openapi.yaml. Produce a reader-first guide that states the contract, calls out retries and cancellation, gives one copyable example, and separates operator advice from application-developer advice.\n\nConstraints:\n- touch generated artifacts only through their checked-in generator\n- leave generated files and vendored code alone\n- retain the current Terraform operational envelope\n\nThis repository spans billing, Elixir, Android; use its existing conventions rather than importing a new abstraction.\n\nProduce durable prose rather than a code assessment or implementation change.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"}
|
||||
{"prompt":"# projects/longbow/crates/index/src/segment.rs\n[worker.longboworbitsyncflow]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.longboworbitsyncflow.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.longboworbitsyncflow.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.LongbowOrbitSyncFlow.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-52144\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\nMake the one confirmed configuration correction in projects/longbow/crates/index/src/segment.rs. 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":"For LongbowWillowCodecCoordinator, find the unknown cause of lost focus when the drawer animation finishes; once that is complete, give the existing implementation a read-only safety pass. Work from projects/longbow/lib/codec/frame.cc, stay with Core Data, and leave generated files and vendored code alone. Keep the two outcomes separately reviewable.","purpose":"debugging","secondary":"review","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"}
|
||||
{"prompt":"Background: The LongbowRainfallDBStore surface in projects/longbow/ui/settings/PrivacyPane.tsx 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":"Ticket OPS-52155: retire the legacy replay path for LongbowPineMetricsCoordinator\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 artifact into a reversible LongbowPineMetricsCoordinator 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":"I inherited LongbowOpalRouterStore and need a careful read of projects/longbow/crates/index/src/segment.rs 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- leave generated files and vendored code alone\n- stay compatible with the existing Terraform deployment\n- keep the work scoped to LongbowOpalRouterStore and its direct tests\n\nThe relevant code crosses billing, Elixir, Android. Prefer evidence from the repository and make any assumption explicit.\n\nReturn an assessment of the existing artifact; only quote enough to make the walkthrough understandable.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"}
|
||||
{"prompt":"LongbowIrisBatchCoordinator: untangle the messy bit","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"}
|
||||
{"prompt":"What sequence would let LongbowQuartzPlayerService adopt Terraform 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.7,"slice":"core","lang":"en"}
|
||||
{"prompt":"diff --git a/projects/longbow/packages/api/openapi.yaml b/projects/longbow/packages/api/openapi.yaml\nindex 62d71aa..90f3c1e 100644\n--- a/projects/longbow/packages/api/openapi.yaml\n+++ b/projects/longbow/packages/api/openapi.yaml\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 LongbowCopperBridgeCoordinator 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.7,"slice":"pasted-context","lang":"en"}
|
||||
{"prompt":"LongbowRavenSessionCoordinator: restructure, then assess","purpose":"refactor","secondary":"review","mixed":true,"difficulty":0.5,"slice":"mixed","lang":"en"}
|
||||
{"prompt":"Question: Ticket OPS-52111: retire the legacy replay path for LongbowCloudReconcilerFlow\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\nMap a safe route from the current LongbowCloudReconcilerFlow 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":"Test Suite 'LongbowRavenSessionFlowTests' started at 2026-07-30 09:22:14.018\nTest Case '-[LongbowRavenSessionFlowTests testRestoresSelectionAfterBackgrounding]' started.\nprojects/longbow/services/ledger/replay.go:144: error: -[LongbowRavenSessionFlowTests 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 '-[LongbowRavenSessionFlowTests 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 LongbowRavenSessionFlow'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":"LongbowSummitProxyCoordinator: could this be clearer","purpose":"review","secondary":null,"mixed":false,"difficulty":0.2,"slice":"vague-eval","lang":"en"}
|
||||
{"prompt":"LongbowEmberRelayStore leaks tasks on shutdown","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"}
|
||||
{"prompt":"Incident timeline — INC-52124\n\n08:02 deploy LongbowFlintTimelineFlow 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 LongbowFlintTimelineFlow 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":"Cadre la migration de LongbowDeltaCanvasService","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"fr"}
|
||||
{"prompt":"# CI job 52112: integration-linux\nrunner: ubuntu-24.04 / amd64 / 8 cores\ntoolchain: Core Data\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] LongbowCraneWorkspaceFlowIntegration.replays_after_timeout ... ok\n[test] LongbowCraneWorkspaceFlowIntegration.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 LongbowCraneWorkspaceFlow 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.8,"slice":"pasted-context","lang":"en"}
|
||||
{"prompt":"We expect LongbowJuniperCLIService to outgrow its current Terraform arrangement next quarter, but changing everything at once would be risky. Propose the module boundaries and migration choreography, compare two viable approaches, and make the risk, cost, and reversibility tradeoffs explicit.\n\nConstraints:\n- leave generated files and vendored code alone\n- stay compatible with the existing Terraform deployment\n- keep the work scoped to LongbowJuniperCLIService and its direct tests\n\nThe relevant code crosses billing, Elixir, Android. Prefer evidence from the repository and make any assumption explicit.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"}
|
||||
{"prompt":"LongbowCoralUploadCoordinator: deal with the small issue","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"vague-eval","lang":"en"}
|
||||
{"prompt":"Observation: Architect a gradual ownership transfer for LongbowRainfallDBFlow across two teams, including module seams, temporary interfaces, observability, handoff criteria, and rollback responsibility.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"}
|
||||
{"prompt":"diff --git a/projects/longbow/pkg/cache/lease.rs b/projects/longbow/pkg/cache/lease.rs\nindex 62d71aa..90f3c1e 100644\n--- a/projects/longbow/pkg/cache/lease.rs\n+++ b/projects/longbow/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\nDeliver the LongbowJuniperCLICoordinator 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.8,"slice":"pasted-context","lang":"en"}
|
||||
{"prompt":"What does LongbowWillowCodecService own?","purpose":"review","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"}
|
||||
{"prompt":"Ticket OPS-52145: retire the legacy replay path for LongbowBeaconStoreFlow\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\n请根据以上上下文完成对应工作，保持 API、兼容性和 rollback，并明确说明证据和取舍。 Using this as the starting evidence, propose a staged LongbowBeaconStoreFlow 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":"Is LongbowMoonlitSDKService safe under cancellation?","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"}
|
||||
{"prompt":"Constraint: # projects/longbow/ml/pipeline/features.py\n[worker.longbownovapickerflow]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.longbownovapickerflow.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.longbownovapickerflow.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.LongbowNovaPickerFlow.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-52115\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/longbow/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":"Request: # projects/longbow/engine/render/atlas.cpp\n[worker.longbowwillowcodecflow]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.longbowwillowcodecflow.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.longbowwillowcodecflow.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.LongbowWillowCodecFlow.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-52132\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\nMake the one confirmed configuration correction in projects/longbow/engine/render/atlas.cpp. Keep retry counts, shutdown grace, dependencies, formatting, and production values exactly as they are.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"pasted-context","lang":"en"}
|
||||
{"prompt":"Assess the LongbowFlintTimelineStore diff","purpose":"review","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"}
|
||||
{"prompt":"How does LongbowQuartzPlayerStore propagate cancellation through the Terraform boundary, and are there code paths where ownership becomes ambiguous? I want your judgment and walkthrough, not new documentation.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"}
|
||||
{"prompt":"Goal: diff --git a/projects/longbow/cmd/exporter/main.py b/projects/longbow/cmd/exporter/main.py\nindex 62d71aa..90f3c1e 100644\n--- a/projects/longbow/cmd/exporter/main.py\n+++ b/projects/longbow/cmd/exporter/main.py\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 LongbowMicaProfileFlow'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":"Before we approve LongbowMosaicGridService, assess whether an accessibility label that reads the internal enum is an actual correctness risk or merely confusing structure.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"}
|
||||
{"prompt":"Symptom: What is the safest way to split projects/longbow/packages/api/openapi.yaml into independently owned modules while LongbowSummitProxyService's public behavior remains frozen for the next release?","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"boundary","lang":"en"}
|
||||
{"prompt":"projects/longbow/ml/pipeline/features.py 里的 LongbowMapleQueueService 最近在 Redis Streams 流程中出现间歇性问题。 请拆分职责并去掉重复，同时保持 API、wire value、顺序和可观察行为不变。\n\n约束：\n- 继续使用 Redis Streams\n- 保持兼容性和取消语义\n- 改动只限于 LongbowMapleQueueService","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"zh"}
|
||||
{"prompt":"Draft LongbowMicaProfileService's upgrade note","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"}
|
||||
{"prompt":"UI ticket DES-52158: finish the compact LongbowHarborIndexCoordinator filter experience\n\nRoute: /catalog/search\nSource: projects/longbow/internal/auth/refresh.go\nFramework: Playwright\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 LongbowHarborIndexCoordinator'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":"Headsup: // projects/longbow/db/migrations/20260730_events.sql\nfinal class LongbowCedarPolicyCoordinatorCoordinator {\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 LongbowCedarPolicyCoordinator; flag semantic changes and missing coverage with exact evidence, keeping this a read-only pass.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.6,"slice":"pasted-context","lang":"en"}
|
||||
{"prompt":"Test Suite 'LongbowDeltaCanvasFlowTests' started at 2026-07-30 09:22:14.018\nTest Case '-[LongbowDeltaCanvasFlowTests testRestoresSelectionAfterBackgrounding]' started.\nprojects/longbow/packages/api/openapi.yaml:144: error: -[LongbowDeltaCanvasFlowTests 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 '-[LongbowDeltaCanvasFlowTests 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 LongbowDeltaCanvasFlow'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":"EXPLAIN (ANALYZE, BUFFERS)\nSELECT e.tenant_id, e.stream_id, max(e.sequence)\nFROM event_log e\nJOIN active_streams s\n ON s.tenant_id = e.tenant_id AND s.id = e.stream_id\nWHERE e.tenant_id = 't_52131'\n AND e.created_at >= now() - interval '24 hours'\nGROUP BY e.tenant_id, e.stream_id;\n\nHashAggregate (cost=184922.10..185011.81 rows=8971 width=40) (actual time=8421.294..8422.551 rows=123 loops=1)\n Group Key: e.tenant_id, e.stream_id\n Batches: 1 Memory Usage: 945kB\n -> Hash Join (cost=2118.42..181004.17 rows=522391 width=32) (actual time=42.118..8279.405 rows=918412 loops=1)\n Hash Cond: ((e.tenant_id = s.tenant_id) AND (e.stream_id = s.id))\n -> Bitmap Heap Scan on event_log e (actual time=18.602..7922.884 rows=1261044 loops=1)\n Recheck Cond: (tenant_id = 't_52131'::text)\n Filter: (created_at >= (now() - '24:00:00'::interval))\n Rows Removed by Filter: 8045512\nPlanning Time: 2.814 ms\nExecution Time: 8423.104 ms\n\nPostgreSQL 17.2, default_statistics_target=100. The same query was under 300 ms last week, no migration landed, and an ANALYZE temporarily returns it to normal.\n\nWire LongbowEmberRelayFlow'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":"LongbowEmberRelayCoordinator needs a paired pass: separate LongbowEmberRelayCoordinator's policy from transport without behavior changes, plus correct the known stale timeout beside it. Use projects/longbow/apps/console/routes/usage.svelte as the source of truth, preserve the React 19 contract, and avoid unrelated cleanup.","purpose":"refactor","secondary":"quickFix","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"}
|
||||
{"prompt":"The API work is done; what remains for LongbowFrostPanelService is the visible interaction layer across loading, offline, empty, and success cases. Bring the drawer and detail pane to production polish with fluid sizing, honest skeletons, focus restoration, accessible announcements, and touch targets that survive large text.\n\nConstraints:\n- cover cancellation, retries, and rollback in the result\n- avoid unrelated changes outside LongbowFrostPanelService\n- leave generated files and vendored code alone\n\nSeveral teams work in this billing, Elixir, Android monorepo, so keep ownership and handoff points understandable in a small review.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"}
|
||||
{"prompt":"Translate the LongbowEchoRegistryStore setup notes","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.2,"slice":"vague-eval","lang":"en"}
|
||||
{"prompt":"FYI: Test Suite 'LongbowMapleQueueFlowTests' started at 2026-07-30 09:22:14.018\nTest Case '-[LongbowMapleQueueFlowTests testRestoresSelectionAfterBackgrounding]' started.\nprojects/longbow/ml/pipeline/features.py:144: error: -[LongbowMapleQueueFlowTests 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 '-[LongbowMapleQueueFlowTests 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 LongbowMapleQueueFlow'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":"LongbowQuartzPlayerCoordinator: ship a sensible version","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"vague-eval","lang":"en"}
|
||||
{"prompt":"Release engineering needs a LongbowDriftConsoleStore 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":"Move LongbowSummitProxyStore's clock and ID generation behind the existing environment type so tests no longer reach global state; outputs and scheduling order must stay identical.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"}
|
||||
{"prompt":"Meanwhile: Test Suite 'LongbowSpruceDaemonFlowTests' started at 2026-07-30 09:22:14.018\nTest Case '-[LongbowSpruceDaemonFlowTests testRestoresSelectionAfterBackgrounding]' started.\nprojects/longbow/config/staging.toml:144: error: -[LongbowSpruceDaemonFlowTests 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 '-[LongbowSpruceDaemonFlowTests 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\nÀ partir de ce contexte, traite la demande indiquée en préservant API, compatibilité et rollback, avec des décisions explicites. Bring LongbowSpruceDaemonFlow'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":"UI ticket DES-52136: finish the compact LongbowKiteSchedulerFlow filter experience\n\nRoute: /catalog/search\nSource: projects/longbow/db/migrations/20260730_events.sql\nFramework: React 19\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 LongbowKiteSchedulerFlow 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":"Could LongbowCedarPolicyFlow show the active React 19 sync phase as an accessible progress row, including reduced-motion behavior?","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"}
|
||||
{"prompt":"Locally: The behavior of LongbowHarborIndexService is stable, yet consumers are reconstructing its contract from tests, Slack threads, and scattered comments in projects/longbow/infra/modules/edge/main.tf. Produce a reader-first guide that states the contract, calls out retries and cancellation, gives one copyable example, and separates operator advice from application-developer advice.\n\nConstraints:\n- touch generated artifacts only through their checked-in generator\n- leave generated files and vendored code alone\n- retain the current Playwright operational envelope\n\nThis repository spans billing, Elixir, Android; use its existing conventions rather than importing a new abstraction.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"}
|
||||
{"prompt":"Introduce a durable deduplication key for LongbowOrbitSyncStore events and enforce it in both the database migration and the ingestion path.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"}
|
||||
{"prompt":"Warum hängt LongbowDeltaCanvasStore?","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"de"}
|
||||
{"prompt":"This should remain a deliberately small patch: LongbowTideWorkerService has one known configuration mistake in projects/longbow/web/components/FilterDrawer.vue, 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- leave generated files and vendored code alone\n- stay compatible with the existing Playwright deployment\n- keep the work scoped to LongbowTideWorkerService and its direct tests\n\nThe relevant code crosses billing, Elixir, Android. Prefer evidence from the repository and make any assumption explicit.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"}
|
||||
{"prompt":"LongbowMicaProfileCoordinator needs a paired pass: separate LongbowMicaProfileCoordinator's policy from transport without behavior changes, plus correct the known stale timeout beside it. Use projects/longbow/ml/pipeline/features.py as the source of truth, preserve the Redis Streams contract, and avoid unrelated cleanup.","purpose":"refactor","secondary":"quickFix","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"}
|
||||
{"prompt":"Production: Ticket OPS-52137: retire the legacy replay path for LongbowVelaDrawerFlow\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\nCom este contexto, trate a solicitação indicada preservando API, compatibilidade e rollback, com decisões e evidências claras. From this evidence, draft consumer-facing migration guidance for LongbowVelaDrawerFlow, 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":"# projects/longbow/Sources/App/SessionStore.swift\n[worker.longbowgarnetmodalflow]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.longbowgarnetmodalflow.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.longbowgarnetmodalflow.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.LongbowGarnetModalFlow.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-52120\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\nMake the one confirmed configuration correction in projects/longbow/Sources/App/SessionStore.swift. Keep retry counts, shutdown grace, dependencies, formatting, and production values exactly as they are.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"pasted-context","lang":"en"}
|
||||
{"prompt":"LongbowSableParserCoordinator: polish, then assess","purpose":"refactor","secondary":"review","mixed":true,"difficulty":0.5,"slice":"mixed","lang":"en"}
|
||||
{"prompt":"LongbowIrisBatchStore's staging timeout is already known to be wrong: change the single projects/longbow/engine/render/atlas.cpp value from 15 to 30 seconds and leave production alone.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"}
|
||||
{"prompt":"LongbowNimbusFormService's frame.cc needs better comments","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"}
|
||||
{"prompt":"LongbowKiteSchedulerService 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 asks around LongbowLumenChartCoordinator: (1) find the unknown cause of a feature flag whose default differs between environments; (2) correct the known stale timeout beside it. Leave generated files and vendored code alone, and leave a clear boundary between the resulting artifacts or edits.","purpose":"debugging","secondary":"quickFix","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"}
|
||||
{"prompt":"LongbowAcornWidgetCoordinator: rethink this area","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.6,"slice":"vague-eval","lang":"en"}
|
||||
{"prompt":"Staging: // projects/longbow/internal/auth/refresh.go\nfinal class LongbowMarbleTokenFlowCoordinator {\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 LongbowMarbleTokenFlow 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":"Enforce LongbowEchoRegistryService's idempotency key","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"}
|
||||
{"prompt":"LongbowBirchMigratorCoordinator needs a paired pass: produce a consumer guide for LongbowBirchMigratorCoordinator, plus give the existing implementation a read-only safety pass. Use projects/longbow/internal/auth/refresh.go as the source of truth, preserve the Playwright contract, and avoid unrelated cleanup.","purpose":"writing","secondary":"review","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"}
|
||||
{"prompt":"Billing: Before touching projects/longbow/infra/modules/edge/main.tf, propose how to retire its legacy format while old clients remain active for ninety days and operators retain a reversible escape hatch.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"}
|
||||
{"prompt":"PM is preparing the LongbowCopperBridgeService 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 LongbowCopperBridgeService\n- leave generated files and vendored code alone\n\nSeveral teams work in this billing, Elixir, Android 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":"In projects/longbow/app/src/main/SyncWorker.kt hat LongbowCloudReconcilerService ein sporadisches Problem im React 19-Ablauf. Lies den aktuellen Ablauf und bewerte Ownership, Abbruch und Reihenfolge; ich brauche nur die Analyse.\n\nRandbedingungen:\n- React 19 weiterverwenden\n- Kompatibilität und Abbruchsemantik erhalten\n- Änderung auf LongbowCloudReconcilerService begrenzen Mache Annahmen explizit, nenne Repository-Belege und bleibe rund um LongbowCloudReconcilerService mit React 19 kompatibel.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"boundary","lang":"de"}
|
||||
{"prompt":"LongbowKiteSchedulerStore's staging timeout is already known to be wrong: change the single projects/longbow/src/sync/reconcile.ts value from 15 to 30 seconds and leave production alone.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"}
|
||||
{"prompt":"A previously stable test around LongbowDriftConsoleService now fails one run in twenty. Determine whether ordering, locale, or leaked state is responsible.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"}
|
||||
{"prompt":"CI: # projects/longbow/web/components/FilterDrawer.vue\n[worker.longbowtideworkerflow]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.longbowtideworkerflow.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.longbowtideworkerflow.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.LongbowTideWorkerFlow.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-52113\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\nCon este contexto, resuelve la petición indicada manteniendo API, compatibilidad y rollback; deja claras las decisiones y la evidencia. Align LongbowTideWorkerFlow'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.3,"slice":"pasted-context","lang":"en"}
|
||||
{"prompt":"Release verification found a single stale LongbowCraneWorkspaceStore 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- leave generated files and vendored code alone\n- retain the current Core Data operational envelope\n\nThis repository spans billing, Elixir, Android; use its existing conventions rather than importing a new abstraction.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"}
|
||||
{"prompt":"Test Suite 'LongbowWrenExportFlowTests' started at 2026-07-30 09:22:14.018\nTest Case '-[LongbowWrenExportFlowTests testRestoresSelectionAfterBackgrounding]' started.\nprojects/longbow/workers/thumbnail/consumer.ex:144: error: -[LongbowWrenExportFlowTests 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 '-[LongbowWrenExportFlowTests 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 LongbowWrenExportFlow'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":"Incident timeline — INC-52116\n\n08:02 deploy LongbowOspreyJobFlow 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 LongbowOspreyJobFlow rollout strategy: phases, dual-operation window, validation, ownership, removal criteria, and explicit stop conditions.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"}
|
||||
{"prompt":"Incident timeline — INC-52126\n\n08:02 deploy LongbowCinderAuthFlow 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 LongbowCinderAuthFlow 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":"Corrija o timeout de LongbowLumenChartService","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.4,"slice":"boundary","lang":"pt"}
|
||||
{"prompt":"Compare the old and new LongbowVelaDrawerService adapters for ordering, error mapping, and shutdown guarantees; report semantic differences without proposing edits.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"}
|
||||
{"prompt":"Bring LongbowPineMetricsStore's confirmation sheet in line with the design tokens, including destructive emphasis, dark appearance, Dynamic Type, and swipe-to-dismiss behavior.","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"}
|
||||
{"prompt":"Ticket OPS-52151: retire the legacy replay path for LongbowSlateEditorCoordinator\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 LongbowSlateEditorCoordinator 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":"Atlas: Test Suite 'LongbowMoonlitSDKFlowTests' started at 2026-07-30 09:22:14.018\nTest Case '-[LongbowMoonlitSDKFlowTests testRestoresSelectionAfterBackgrounding]' started.\nprojects/longbow/apps/console/routes/usage.svelte:144: error: -[LongbowMoonlitSDKFlowTests 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 '-[LongbowMoonlitSDKFlowTests 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\nBearbeite auf Basis dieses Kontexts die beschriebene Aufgabe; API, Kompatibilität und Rollback müssen erhalten bleiben. Finish the visible LongbowMoonlitSDKFlow state described above: responsive layout, correct selection restoration, keyboard focus, accessible labels, dark mode, and reduced-motion behavior.","purpose":"frontendImpl","secondary":"debugging","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"}
|
||||
{"prompt":"LongbowMosaicGridCoordinator: take care of the warning","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"}
|
||||
{"prompt":"LongbowPrismCacheCoordinator: ship, then assess","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"}
|
||||
{"prompt":"Compare the old and new LongbowAtlasSearchStore adapters for ordering, error mapping, and shutdown guarantees; report semantic differences without proposing edits. I want your judgment and walkthrough, not new documentation.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"}
|
||||
{"prompt":"Ticket OPS-52110: retire the legacy replay path for LongbowAsterWebhookFlow\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 LongbowAsterWebhookFlow 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":"// projects/longbow/pkg/cache/lease.rs\nfinal class LongbowOpalRouterFlowCoordinator {\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 LongbowOpalRouterFlow 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":"Persist LongbowLedgerGateFlow delivery attempts in projects/longbow/services/ledger/replay.go, claim them safely across workers, and make duplicate webhook receipts return the original accepted result.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"}
|
||||
{"prompt":"Two asks around LongbowFlintTimelineCoordinator: (1) finish LongbowFlintTimelineCoordinator's responsive empty and retry states; (2) give the existing implementation a read-only safety pass. Leave generated files and vendored code alone, and leave a clear boundary between the resulting artifacts or edits.","purpose":"frontendImpl","secondary":"review","mixed":true,"difficulty":0.7,"slice":"mixed","lang":"en"}
|
||||
{"prompt":"PM needs a concise migration note for LongbowOrbitSyncService, 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":"Beacon: Release engineering needs a LongbowJuniperCLIStore changelog entry that distinguishes operator action from invisible internal cleanup and names the rollback condition.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.2,"slice":"core","lang":"en"}
|
||||
{"prompt":"Extract LongbowOspreyJobService's parsing loop","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"}
|
||||
{"prompt":"LongbowAsterWebhookCoordinator is blocking the next release because cancellation being swallowed at the repository boundary. I need two concrete outcomes from a single pass: lay out a staged migration for LongbowAsterWebhookCoordinator, and consolidate the duplicated normalization paths without changing behavior. Use the existing Redis Streams conventions in projects/longbow/Sources/App/SessionStore.swift; leave generated files and vendored code alone. 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":"planning","secondary":"refactor","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"}
|
||||
{"prompt":"Ownership of LongbowFernSnapshotService 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- leave generated files and vendored code alone\n- retain the current Core Data operational envelope\n\nThis repository spans billing, Elixir, Android; use its existing conventions rather than importing a new abstraction.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"}
|
||||
{"prompt":"LongbowAmberFilterCoordinator: maybe tighten this up","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"}
|
||||
{"prompt":"The public surface of LongbowAsterWebhookStore is frozen, but its internal ownership in projects/longbow/Sources/App/SessionStore.swift 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 LongbowAsterWebhookStore\n- leave generated files and vendored code alone\n\nSeveral teams work in this billing, Elixir, Android monorepo, so keep ownership and handoff points understandable in a small review.","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"}
|
||||
{"prompt":"Cinder: Ticket OPS-52117: retire the legacy replay path for LongbowPrismCacheFlow\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 LongbowPrismCacheFlow 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":"For LongbowCinderAuthCoordinator, assess ownership and failure handling in projects/longbow/db/migrations/20260730_events.sql; once that is complete, capture the contract and rollback note for consumers. Work from projects/longbow/db/migrations/20260730_events.sql, stay with React 19, and leave generated files and vendored code alone. Keep the two outcomes separately reviewable.","purpose":"review","secondary":"writing","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"}
|
||||
{"prompt":"Spell LongbowSableParserStore's metric correctly","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"}
|
||||
{"prompt":"Introduce a durable deduplication key for LongbowCoralUploadService events and enforce it in both the database migration and the ingestion path.","purpose":"backendImpl","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"}
|
||||
{"prompt":"Assess the LongbowWillowCodecStore diff","purpose":"review","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"}
|
||||
{"prompt":"# CI job 52127: integration-linux\nrunner: ubuntu-24.04 / amd64 / 8 cores\ntoolchain: Core Data\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] LongbowLumenChartFlowIntegration.replays_after_timeout ... ok\n[test] LongbowLumenChartFlowIntegration.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\nDetermine why LongbowLumenChartFlow produces this result. Trace ordering, cancellation, shared state, and scheduler behavior; identify the root cause before suggesting a patch.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"pasted-context","lang":"en"}
|
||||
{"prompt":"Check LongbowNovaPickerService's trust boundary","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"}
|
||||
{"prompt":"LongbowTideWorkerCoordinator is blocking the next release because out-of-order events after consumer rebalancing. I need two concrete outcomes from a single pass: change LongbowTideWorkerCoordinator's known staging timeout from 15 to 30 seconds, and capture the contract and rollback note for consumers. Use the existing Playwright conventions in projects/longbow/services/ledger/replay.go; leave generated files and vendored code alone. 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":"quickFix","secondary":"writing","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"}
|
||||
{"prompt":"Unify the LongbowSpruceDaemonService validators","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"}
|
||||
{"prompt":"Delta: projects/longbow/services/ledger/replay.go の LongbowAmberFilterService で、Playwright の flow に断続的な問題が起きています。 責務を分離して重複をなくし、API、wire value、順序、観測可能な動作は変えないでください。\n\n制約:\n- Playwright を継続利用\n- 互換性と cancel の意味を維持\n- 変更範囲は LongbowAmberFilterService のみ","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"ja"}
|
||||
{"prompt":"LongbowVelaDrawerCoordinator: give it a nicer flow","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"}
|
||||
{"prompt":"Ember: Two deliverables are holding up LongbowCloudReconcilerCoordinator. First, find the unknown cause of a feature flag whose default differs between environments. In the same workstream, give the existing implementation a read-only safety pass. The relevant starting point is projects/longbow/apps/console/routes/usage.svelte, which follows React 19 conventions and currently suffers from a feature flag whose default differs between environments. Leave generated files and vendored code alone.\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":"debugging","secondary":"review","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"}
|
||||
{"prompt":"Animate the LongbowBasilRunnerStore drawer","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"}
|
||||
{"prompt":"Frost: Compare LongbowGarnetModalService's two adapters","purpose":"review","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"}
|
||||
{"prompt":"# projects/longbow/internal/auth/refresh.go\n[worker.longbowsableparserflow]\nenabled = true\nrequest_timeout_seconds = 15\nshutdown_grace_seconds = 10\nmax_in_flight = 32\nretry_attempts = 4\nretry_base_milliseconds = 250\n\n[worker.longbowsableparserflow.staging]\nrequest_timeout_seconds = 15\nemit_debug_spans = true\n\n[worker.longbowsableparserflow.production]\nrequest_timeout_seconds = 30\nemit_debug_spans = false\n\nFailing assertion:\n ConfigTests.LongbowSableParserFlow.staging_timeout_matches_supported_gateway\n expected: Duration.seconds(30)\n actual: Duration.seconds(15)\n\nTicket note CFG-52118\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/longbow/internal/auth/refresh.go and its adjacent assertion. Avoid broader cleanup.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.2,"slice":"pasted-context","lang":"en"}
|
||||
{"prompt":"LongbowOspreyJobCoordinator: correct, then document","purpose":"quickFix","secondary":"writing","mixed":true,"difficulty":0.4,"slice":"mixed","lang":"en"}
|
||||
{"prompt":"Trace LongbowBasilRunnerService's memory growth","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"}
|
||||
{"prompt":"Outline a safer LongbowFlintTimelineService cutover","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"}
|
||||
{"prompt":"Draft LongbowRavenSessionStore's upgrade note","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"}
|
||||
{"prompt":"Garnet: PM is preparing the LongbowCraneWorkspaceService 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 LongbowCraneWorkspaceService\n- leave generated files and vendored code alone\n\nSeveral teams work in this billing, Elixir, Android 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":"Please turn LongbowCopperBridgeFlow's existing tests into a short contract reference, covering pagination, malformed input, authorization, and retry semantics without copying test code.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.4,"slice":"core","lang":"en"}
|
||||
{"prompt":"Nobody is asking for code changes yet; we first need to understand whether the current LongbowCedarPolicyService 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 LongbowCedarPolicyService\n- leave generated files and vendored code alone\n\nSeveral teams work in this billing, Elixir, Android 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":"The LongbowVelaDrawerStore surface in projects/longbow/workers/thumbnail/consumer.ex 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.3,"slice":"core","lang":"en"}
|
||||
{"prompt":"Harbor: // projects/longbow/apps/console/routes/usage.svelte\nfinal class LongbowAtlasSearchFlowCoordinator {\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 LongbowAtlasSearchFlow; 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":"We expect LongbowPrismCacheStore to outgrow its current Core Data arrangement next quarter, but changing everything at once would be risky. Propose the module boundaries and migration choreography, compare two viable approaches, and make the risk, cost, and reversibility tradeoffs explicit.\n\nConstraints:\n- leave generated files and vendored code alone\n- stay compatible with the existing Core Data deployment\n- keep the work scoped to LongbowPrismCacheStore and its direct tests\n\nThe relevant code crosses billing, Elixir, Android. Prefer evidence from the repository and make any assumption explicit.","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.9,"slice":"core","lang":"en"}
|
||||
{"prompt":"A previously stable test around LongbowFernSnapshotStore now fails one run in twenty. Determine whether ordering, locale, or leaked state is responsible.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"}
|
||||
{"prompt":"LongbowOrbitSyncCoordinator: why is this odd","purpose":"review","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"}
|
||||
{"prompt":"Since the last release, LongbowSlateEditorService has shown a feature flag whose default differs between environments; nobody on the team can reproduce it reliably on a laptop. Trace task lifetime, cursor advancement, and durable acknowledgment across reconnects; produce a defensible root cause and the smallest experiment that would falsify it.\n\nConstraints:\n- leave generated files and vendored code alone\n- stay compatible with the existing React 19 deployment\n- keep the work scoped to LongbowSlateEditorService and its direct tests\n\nThe relevant code crosses billing, Elixir, Android. Prefer evidence from the repository and make any assumption explicit.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.8,"slice":"core","lang":"en"}
|
||||
{"prompt":"LongbowAcornWidgetStore's staging timeout is already known to be wrong: change the single projects/longbow/internal/auth/refresh.go value from 15 to 30 seconds and leave production alone.","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"}
|
||||
{"prompt":"Iris: Ticket OPS-52140: retire the legacy replay path for LongbowMosaicGridFlow\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 LongbowMosaicGridFlow 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":"Em projects/longbow/cmd/exporter/main.py, o LongbowMapleQueueStore tem um problema intermitente no fluxo de Redis Streams. Separe responsabilidades e remova duplicação sem mudar API, wire values, ordem ou comportamento observável.\n\nRestrições:\n- continuar com Redis Streams\n- preservar compatibilidade e cancelamento\n- limitar a mudança ao LongbowMapleQueueStore","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"pt"}
|
||||
{"prompt":"Trace LongbowGarnetModalStore's memory growth","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"}
|
||||
{"prompt":"UI ticket DES-52148: finish the compact LongbowAcornWidgetFlow filter experience\n\nRoute: /catalog/search\nSource: projects/longbow/infra/modules/edge/main.tf\nFramework: Playwright\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 LongbowAcornWidgetFlow 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":"Juniper: Ticket OPS-52149: retire the legacy replay path for LongbowQuartzPlayerFlow\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 artifact into a reversible LongbowQuartzPlayerFlow 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":"Two asks around LongbowBasilRunnerCoordinator: (1) separate LongbowBasilRunnerCoordinator's policy from transport without behavior changes; (2) capture the contract and rollback note for consumers. Leave generated files and vendored code alone, and leave a clear boundary between the resulting artifacts or edits.","purpose":"refactor","secondary":"writing","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"}
|
||||
{"prompt":"Kestrel: The public surface of LongbowTideWorkerStore is frozen, but its internal ownership in projects/longbow/services/ledger/replay.go 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 LongbowTideWorkerStore\n- leave generated files and vendored code alone\n\nSeveral teams work in this billing, Elixir, Android 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":"LongbowBeaconStoreCoordinator: polish the last piece","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.3,"slice":"vague-eval","lang":"en"}
|
||||
{"prompt":"Is there a cleaner way to separate LongbowSlateEditorStore'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.6,"slice":"core","lang":"en"}
|
||||
{"prompt":"Remove LongbowSableParserService's stray comma","purpose":"quickFix","secondary":null,"mixed":false,"difficulty":0.1,"slice":"core","lang":"en"}
|
||||
{"prompt":"Lumen: Two asks around LongbowEchoRegistryCoordinator: (1) separate LongbowEchoRegistryCoordinator's policy from transport without behavior changes; (2) capture the contract and rollback note for consumers. Leave generated files and vendored code alone, 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":"For LongbowSpruceDaemonCoordinator, lay out a staged migration for LongbowSpruceDaemonCoordinator; once that is complete, also add the visible loading and offline states. Work from projects/longbow/packages/api/openapi.yaml, stay with Terraform, and leave generated files and vendored code alone. Keep the two outcomes separately reviewable.","purpose":"planning","secondary":"frontendImpl","mixed":true,"difficulty":0.8,"slice":"mixed","lang":"en"}
|
||||
{"prompt":"LongbowAtlasSearchCoordinator: the screen feels unfinished","purpose":"frontendImpl","secondary":null,"mixed":false,"difficulty":0.4,"slice":"vague-eval","lang":"en"}
|
||||
{"prompt":"Maple: The LongbowFrostPanelFlow 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":"LongbowGarnetModalCoordinator: ship, then assess","purpose":"frontendImpl","secondary":"review","mixed":true,"difficulty":0.6,"slice":"mixed","lang":"en"}
|
||||
{"prompt":"diff --git a/projects/longbow/ui/settings/PrivacyPane.tsx b/projects/longbow/ui/settings/PrivacyPane.tsx\nindex 62d71aa..90f3c1e 100644\n--- a/projects/longbow/ui/settings/PrivacyPane.tsx\n+++ b/projects/longbow/ui/settings/PrivacyPane.tsx\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 LongbowRainfallDBCoordinator'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/longbow/src/sync/reconcile.ts\nfinal class LongbowCoralUploadFlowCoordinator {\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 LongbowCoralUploadFlow'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"}
|
||||
{"prompt":"LongbowKiteSchedulerCoordinator: clean up that old path","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"}
|
||||
{"prompt":"Nimbus: // projects/longbow/lib/codec/frame.cc\nfinal class LongbowNimbusFormFlowCoordinator {\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 LongbowNimbusFormFlow'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"}
|
||||
{"prompt":"LongbowMosaicGridStore 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":"Ticket OPS-52152: retire the legacy replay path for LongbowFernSnapshotCoordinator\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 LongbowFernSnapshotCoordinator 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":"LongbowLumenChartStore est-il sûr ?","purpose":"review","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"fr"}
|
||||
{"prompt":"Incident timeline — INC-52142\n\n08:02 deploy LongbowIrisBatchFlow 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\nUsing this as the starting evidence, propose a staged LongbowIrisBatchFlow 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":"The behavior of LongbowNovaPickerStore is stable, yet consumers are reconstructing its contract from tests, Slack threads, and scattered comments in projects/longbow/cmd/exporter/main.py. Produce a reader-first guide that states the contract, calls out retries and cancellation, gives one copyable example, and separates operator advice from application-developer advice.\n\nConstraints:\n- touch generated artifacts only through their checked-in generator\n- leave generated files and vendored code alone\n- retain the current Redis Streams operational envelope\n\nThis repository spans billing, Elixir, Android; use its existing conventions rather than importing a new abstraction.\n\nProduce durable prose rather than a code assessment or implementation change.","purpose":"writing","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"}
|
||||
{"prompt":"Nobody is asking for code changes yet; we first need to understand whether the current LongbowOspreyJobStore 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 LongbowOspreyJobStore\n- leave generated files and vendored code alone\n\nSeveral teams work in this billing, Elixir, Android monorepo, so keep ownership and handoff points understandable in a small review.\n\nReturn an assessment of the existing artifact; only quote enough to make the walkthrough understandable.","purpose":"review","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"en"}
|
||||
{"prompt":"Incident timeline — INC-52134\n\n08:02 deploy LongbowDriftConsoleFlow 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 LongbowDriftConsoleFlow, 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":"LongbowDriftConsoleCoordinator: sort out the rough edge","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"vague-eval","lang":"en"}
|
||||
{"prompt":"En projects/longbow/services/ledger/replay.go, LongbowLedgerGateService tiene un problema intermitente en el flujo de Playwright. Sigue queue, scheduler y cancelación, compara hipótesis y encuentra la causa antes de proponer cambios.\n\nRestricciones:\n- seguir con Playwright\n- conservar compatibilidad y cancelación\n- limitar el cambio a LongbowLedgerGateService Explicita los supuestos, señala la evidencia del repositorio y mantén compatibilidad con Playwright alrededor de LongbowLedgerGateService.","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"es"}
|
||||
{"prompt":"Test Suite 'LongbowAmberFilterFlowTests' started at 2026-07-30 09:22:14.018\nTest Case '-[LongbowAmberFilterFlowTests testRestoresSelectionAfterBackgrounding]' started.\nprojects/longbow/services/ledger/replay.go:144: error: -[LongbowAmberFilterFlowTests 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 '-[LongbowAmberFilterFlowTests 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 LongbowAmberFilterFlow'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":"LongbowDeltaCanvasCoordinator: document, then assess","purpose":"writing","secondary":"review","mixed":true,"difficulty":0.4,"slice":"mixed","lang":"en"}
|
||||
{"prompt":"LongbowNimbusFormCoordinator: document, then assess","purpose":"writing","secondary":"review","mixed":true,"difficulty":0.4,"slice":"mixed","lang":"en"}
|
||||
{"prompt":"Milestones for replacing LongbowMicaProfileStore","purpose":"planning","secondary":null,"mixed":false,"difficulty":0.6,"slice":"core","lang":"en"}
|
||||
{"prompt":"Opal: The minimum supported Core Data version in projects/longbow/lib/codec/frame.cc 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":"Find LongbowNimbusFormStore's duplicate retry source","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.5,"slice":"core","lang":"en"}
|
||||
{"prompt":"Prism: projects/longbow/apps/console/routes/usage.svelte の LongbowSlateEditorFlow で、React 19 の flow に断続的な問題が起きています。 現在の flow を読み、ownership、cancel、順序が安全か評価してください。分析だけで十分です。\n\n制約:\n- React 19 を継続利用\n- 互換性と cancel の意味を維持\n- 変更範囲は LongbowSlateEditorFlow のみ","purpose":"debugging","secondary":null,"mixed":false,"difficulty":0.7,"slice":"core","lang":"ja"}
|
||||
{"prompt":"Rename LongbowSpruceDaemonStore's staleLease state","purpose":"refactor","secondary":null,"mixed":false,"difficulty":0.3,"slice":"core","lang":"en"}
|
||||
|
||||
Reference in New Issue
Block a user